X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/9243700fb212c2508c4d4c80fb8eb968e565e44d..a01ada0599acdc11497850c4c8e846d3f237bf91:/include/wx/unix/apptrait.h diff --git a/include/wx/unix/apptrait.h b/include/wx/unix/apptrait.h index 3c172d803b..d29686af57 100644 --- a/include/wx/unix/apptrait.h +++ b/include/wx/unix/apptrait.h @@ -22,7 +22,6 @@ public: #if wxUSE_CONSOLE_EVENTLOOP virtual wxEventLoopBase *CreateEventLoop(); #endif // wxUSE_CONSOLE_EVENTLOOP - virtual int WaitForChild(wxExecuteData& execData); #if wxUSE_TIMER virtual wxTimerImpl *CreateTimerImpl(wxTimer *timer); #endif @@ -30,11 +29,30 @@ public: #if wxUSE_GUI -class WXDLLEXPORT wxGUIAppTraits : public wxGUIAppTraitsBase +// 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_PROCESS_CALLBACKS + #define wxHAS_GUI_SOCKET_MANAGER +#endif + +#ifdef __DARWIN__ + #define wxHAS_GUI_PROCESS_CALLBACKS +#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 @@ -46,7 +64,7 @@ public: #if (defined(__WXMAC__) || defined(__WXCOCOA__)) && wxUSE_STDPATHS virtual wxStandardPathsBase& GetStandardPaths(); #endif - virtual wxPortId GetToolkitVersion(int *majVer, int *minVer) const; + virtual wxPortId GetToolkitVersion(int *majVer = NULL, int *minVer = NULL) const; #if defined(__WXGTK__) && wxUSE_INTL virtual void SetLocale(); @@ -62,15 +80,8 @@ public: virtual bool ShowAssertDialog(const wxString& msg); #endif - // GTK+ and Motif integrate sockets directly in their main loop, the other - // Unix ports do it at wxEventLoop level - // - // 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 wxUSE_SOCKETS && (defined(__WXGTK__) || defined(__WXMOTIF__)) - virtual GSocketManager *GetSocketManager(); +#if wxUSE_SOCKETS && defined(wxHAS_GUI_SOCKET_MANAGER) + virtual wxSocketManager *GetSocketManager(); #endif };