summaryrefslogtreecommitdiff
path: root/gtk/gtkapplication-quartz.c
Commit message (Collapse)AuthorAgeFilesLines
* Drop gtk_application_is_inhibitedMatthias Clasen2017-11-281-13/+0
| | | | | | | | This function returns global session state that may not be available to applications (e.g. in sandboxed environments), and is not needed by applications, so just drop it, instead of keeping a function around that can't be guaranteed to work.
* Replace deprecated gtk_application_add_acceleratorJohn Ralls2014-08-031-4/+8
| | | | With new gtk_application_set_accels_for_action.
* resources: move resources into a subdirectoryWilliam Jon McCann2014-01-231-1/+1
|
* quartz: add a default application menuRyan Lortie2014-01-171-4/+66
| | | | | | | | | | | | | | | | | When running on quartz, it is no longer expected for applications to provide their own application menu. Instead, they should simply ensure that they provide "app.about", "app.preferences" and "app.quit" actions (which many apps are already doing). A default menu will be shown that looks like the one presented by all other Mac OS applications, containing menu items for the above actions, as well as the typical "Hide app", "Hide Others and "Show All" items and the "Services" submenu. If an application does explicitly set an application menu (via gtk_application_set_app_menu()) then it will be respected, as before. https://bugzilla.gnome.org/show_bug.cgi?id=720552
* Use GtkMenuTracker for Quartz backend.William Hua2014-01-081-20/+52
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=710351
* gtkapplication-quartz: clean up inhibit codeRyan Lortie2014-01-071-53/+31
| | | | | | | | When testing with bloatpad, the existing inhibit code seems not to be working at all. Replace it with a cleaner and simpler version that works. https://bugzilla.gnome.org/show_bug.cgi?id=720551
* Refactor GtkApplicationRyan Lortie2013-12-161-0/+262
gtkapplication.c has turned into a bit of an #ifdef mess over time, and many of the current checks are incorrect. As an example, if you build Gtk for wayland, and exclude the X11 backend, much of the functionality required by wayland (such as exporting menu models) will be disabled. Solve that by introducing a backend mechanism to GtkApplication (named GtkApplicationImpl) similar to the one in GApplication. Add backends for Wayland, X11 and Quartz, with X11 and Wayland sharing a common 'DBus' superclass. GtkApplicationImpl | /--------------+-------------------\ | | GtkApplicationImplDBus GtkApplicationImplQuartz | /-----------+-----------------\ | | GtkApplicationImplX11 GtkApplicationImplWayland GtkApplicationImpl itself is essentially a bunch of vfuncs that serve as hooks for various things that the platform-specific backends may be interested in doing (startup, shutdown, managing windows, inhibit, etc.) With this change, all platform specific code has been removed from gtkapplication.c and gtkapplicationwindow.c (both of which are now free of #ifdefs, except for a UNIX-specific use of GDesktopAppInfo in gtkapplicationwindow.c). Additionally, because of the movement of the property-setting code out of GtkApplicationWindow, the _GTK_APPLICATION_ID properties (and friends) will be set on non-GtkApplicationWindows, such as dialogs. https://bugzilla.gnome.org/show_bug.cgi?id=720550