b51014176a
This undoes the changes of r44773 because calling setlocale() resulted in C locale being set differently from C++ locale which was confusing and led to huge slowdowns in any code using std::stream with at least MinGW. And setting the C++ locale to be the same, as r72719 tried to do, doesn't seem to be practical as it results in immediate crashes under OS X and MinGW when used under XP. Do provide wxApp::SetCLocale() helper to explicitly do what was previously done implicitly, even though currently it is a trivial wrapper for setlocale() and we don't even need to call gtk_set_locale() as it has never done anything else and is deprecated since GTK+ 2.24. Closes #14780. git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@72951 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
97 lines
3.0 KiB
C++
97 lines
3.0 KiB
C++
///////////////////////////////////////////////////////////////////////////////
|
|
// Name: wx/unix/apptrait.h
|
|
// Purpose: standard implementations of wxAppTraits for Unix
|
|
// Author: Vadim Zeitlin
|
|
// Modified by:
|
|
// Created: 23.06.2003
|
|
// RCS-ID: $Id$
|
|
// Copyright: (c) 2003 Vadim Zeitlin <vadim@wxwidgets.org>
|
|
// Licence: wxWindows licence
|
|
///////////////////////////////////////////////////////////////////////////////
|
|
|
|
#ifndef _WX_UNIX_APPTRAIT_H_
|
|
#define _WX_UNIX_APPTRAIT_H_
|
|
|
|
// ----------------------------------------------------------------------------
|
|
// wxGUI/ConsoleAppTraits: must derive from wxAppTraits, not wxAppTraitsBase
|
|
// ----------------------------------------------------------------------------
|
|
|
|
class WXDLLIMPEXP_BASE wxConsoleAppTraits : public wxConsoleAppTraitsBase
|
|
{
|
|
public:
|
|
#if wxUSE_CONSOLE_EVENTLOOP
|
|
virtual wxEventLoopBase *CreateEventLoop();
|
|
#endif // wxUSE_CONSOLE_EVENTLOOP
|
|
#if wxUSE_TIMER
|
|
virtual wxTimerImpl *CreateTimerImpl(wxTimer *timer);
|
|
#endif
|
|
};
|
|
|
|
#if wxUSE_GUI
|
|
|
|
// GTK+ and Motif integrate sockets and child processes monitoring directly in
|
|
// their main loop, the other Unix ports do it at wxEventLoop level and so use
|
|
// the non-GUI traits and don't need anything here
|
|
//
|
|
// TODO: Should we use XtAddInput() for wxX11 too? Or, vice versa, if there is
|
|
// no advantage in doing this compared to the generic way currently used
|
|
// by wxX11, should we continue to use GTK/Motif-specific stuff?
|
|
#if defined(__WXGTK__) || defined(__WXMOTIF__)
|
|
#define wxHAS_GUI_FDIOMANAGER
|
|
#define wxHAS_GUI_PROCESS_CALLBACKS
|
|
#endif // ports using wxFDIOManager
|
|
|
|
#if defined(__WXMAC__)
|
|
#define wxHAS_GUI_PROCESS_CALLBACKS
|
|
#define wxHAS_GUI_SOCKET_MANAGER
|
|
#endif
|
|
|
|
class WXDLLIMPEXP_CORE wxGUIAppTraits : public wxGUIAppTraitsBase
|
|
{
|
|
public:
|
|
virtual wxEventLoopBase *CreateEventLoop();
|
|
virtual int WaitForChild(wxExecuteData& execData);
|
|
#ifdef wxHAS_GUI_PROCESS_CALLBACKS
|
|
virtual int AddProcessCallback(wxEndProcessData *data, int fd);
|
|
#endif
|
|
#if wxUSE_TIMER
|
|
virtual wxTimerImpl *CreateTimerImpl(wxTimer *timer);
|
|
#endif
|
|
#if wxUSE_THREADS && defined(__WXGTK20__)
|
|
virtual void MutexGuiEnter();
|
|
virtual void MutexGuiLeave();
|
|
#endif
|
|
|
|
#if (defined(__WXMAC__) || defined(__WXCOCOA__)) && wxUSE_STDPATHS
|
|
virtual wxStandardPaths& GetStandardPaths();
|
|
#endif
|
|
virtual wxPortId GetToolkitVersion(int *majVer = NULL, int *minVer = NULL) const;
|
|
|
|
#ifdef __WXGTK20__
|
|
virtual wxString GetDesktopEnvironment() const;
|
|
virtual wxString GetStandardCmdLineOptions(wxArrayString& names,
|
|
wxArrayString& desc) const;
|
|
#endif // __WXGTK20____
|
|
|
|
#if defined(__WXGTK20__)
|
|
virtual bool ShowAssertDialog(const wxString& msg);
|
|
#endif
|
|
|
|
#if wxUSE_SOCKETS
|
|
|
|
#ifdef wxHAS_GUI_SOCKET_MANAGER
|
|
virtual wxSocketManager *GetSocketManager();
|
|
#endif
|
|
|
|
#ifdef wxHAS_GUI_FDIOMANAGER
|
|
virtual wxFDIOManager *GetFDIOManager();
|
|
#endif
|
|
|
|
#endif // wxUSE_SOCKETS
|
|
};
|
|
|
|
#endif // wxUSE_GUI
|
|
|
|
#endif // _WX_UNIX_APPTRAIT_H_
|
|
|