| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
|
|
|
|
|
|
|
|
|
| |
Demos in gtk-demo are supposed to be exemplary. However, if one were to
give them dummy main functions many of them would not compile with
-DGSEAL_ENABLE. This changes the demos to make them use accessor
functions whenever possible instead of direct changes to the struct
members.
http://bugzilla.gnome.org/show_bug.cgi?id=667155
|
|
|
|
|
|
| |
Explicitly return FALSE in selection_set_compound_text() to
indicate that we don't want to support compound text selections;
this will eliminate the "not implemented" warning for quartz.
|
|
|
|
|
|
|
|
|
| |
This pushes the clipboard contents to the OS X clipboard when the
application is quit. Without doing this, clipboard data set by a GTK+
application cannot be accessed after the clipboard has been quit.
Currently, we implement this the easy way because the clipboard
support is fully implemented in GTK+. In the future this might change.
|
|
|
|
|
|
|
| |
Before, right click events were still let through into GDK. In this
case, also middle/right button events with x-coordinates in the range
[-3, 0] are processed, resulting in failures/crashes in the window
finding code because no GdkWindows are present in this range.
|
|
|
|
|
|
| |
Turn dead_doubleacute plus space into '"' and not into a double
acute because that's the way to enter double quotes on the
US-International keyboard layout.
|
|
|
|
| |
which is delivered by the US-International keyboard layout.
|
|
|
|
|
|
|
| |
The window's role is 'GtkFileChooserDialog', so that window managers can match it
for positioning.
Signed-off-by: Federico Mena Quintero <federico@gnome.org>
|
| |
|
|
|
|
| |
Fix up accesses of ipp structures in gtkcupsutils.c
|
|
|
|
|
|
| |
Having refactored cups_request_printer_list_cb so that the cups
version-dependent block size is small enough to be handled in a single
ifdef, make the ifdef HAVE_CUPS_API_1_6 block
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
So that it can be passed as a single parameter to functions as we
extract-function to make cups_request_printer_list_cb more manageable.
Note that not all of the affected variables are changed in this
changeset. Those are in extracted functions and will be addressed in the
next two changes.
|
|
|
|
| |
Fixes "magic number" in printer_state_reason_level.
|
|
|
|
|
| |
So that they can be used from more than one function. Rename them to
avoid naming conflicts.
|
|
|
|
|
| |
The first, simple changes. Turns off the deprecation warnings and
substitutes macros and short ifdef blocks where feasible.
|
|
|
|
|
|
|
|
| |
In GTK+ 2, child widgets don't get unmapped, and yet, that is when we were trying to
save the settings of GtkFileChooserDefault. Now we connect to the toplevel's
unmap signal and do the right thing there.
Signed-off-by: Federico Mena Quintero <federico@gnome.org>
|
| |
|
|
|
|
|
|
|
| |
Of course, we must pass coordinates in the NSWindow coordinate system
when creating an NSEvent. This fixes drag icon positioning and makes
the icon slide back to the correct position when the drag is
canceled.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In the Quartz backend, there are two methods by which windows are
resized. The first method is fully handled by Quartz and does not appear
in the event stream the application resizes. The second method is when
we resize windows by ourselves. In OS X this happens when a GTK+ resize
grip is used. This resize grip is larger than the Quartz resize grip.
When the resize is started outside the "Quartz area", we have to handle
it by ourselves.
This patch fixes this manual window resizing by ignoring events while we
are in the process of resizing (such that the events actually arrive at
the sendEvent handler of GdkQuartzWindow where this resize is handled).
When the resize has finished we break all grabs such that GDK is not
stuck thinking the cursor is still in the resize window.
|
|
|
|
| |
Function was renamed to _gdk_quartz_events_break_all_grabs().
|
|
|
|
|
|
|
|
|
|
|
| |
When GtkPrinterFunc always returns FALSE, for example when looking for
a non existent printer, if print list is done for all backends or print
backend status is UNAVAILABLE, gtk_enumerate_printers() finishes with an
empty backend list and destroy function is never called. We need to
check the backend list again after calling list_printers_init for all
backends and finish the enumeration if it's empty.
https://bugzilla.gnome.org/show_bug.cgi?id=672125
|
| |
|
|
|
|
|
|
| |
As dieterv said, gtk 2.24 win32 binaries have been frozen on
glib 2.28.x, and we dont have resources rigth now to ensure pygobject
static bindings still function correctly with newer glib versions
|
|
|
|
|
| |
As we use g_format_size() now
See commit 2bedcd8863a88f1e1aea15494dc1995e84a49133
|
|
|
|
|
| |
We do this like in commit 4ead7b69ea0, so that apps which use the gtk2 file chooser
will show the same file sizes as gtk3 apps.
|
|
|
|
| |
... when the iconview is not the only child in it's parent GdkWindow.
|
|
|
|
|
|
|
|
|
| |
If the Window Manager supports the _NET_WM_STATE_HIDDEN, we use it to use
the _NET_WM_STATE protocol when de-iconifying windows (iconification is
unchanged, via XIconifyWindow). Additionally, we no longer interpret all
UnmapNotify events for our window as the result of iconification.
(Based on patch by Tomas Frydrych <tf@linux.intel.com>)
|
|
|
|
| |
Remove LDDADS and setting each object file's LDDAD to it; just set a global LDDAD.
|
| |
|
|
|
|
|
|
|
|
|
| |
The F keys have no unicode mapping, and UCKeyTranslate() returns
a bogus 0x10 as mapping to unicode. Instead of checking for this
random and undocumented return value, simply assign all function
keys explicitly. This patch also splits the ill-named "known_keys"
array into "modifier_keys" and "function_keys" which is much
more obvious.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
_gdk_x11_keymap_key_is_modifier() never tries to set min/max_keycode
if they haven't been set before, meaning that until another function
sets those, all the keys will be seen as non-modifiers.
This causes GdkKeyEvents to be wrongly tagged with "->is_modifier = 0"
when in actual fact the key is a modifier. This fixes keyboard
shortcuts captured with GtkCellRendererAccel in "raw" mode thinking
a modifier without any actual keys is a valid shortcut.
https://bugzilla.gnome.org/show_bug.cgi?id=670400
Conflicts:
gdk/x11/gdkkeys-x11.c
|
|
|
|
| |
Pointed out in bug 643131 and bug 640308.
|
|
|
|
|
| |
Reported by Mike Massonnet in bug
https://bugzilla.gnome.org/show_bug.cgi?id=670093
|
|
|
|
|
|
|
| |
Avoid NULL-pointer dereference when package installation directory
doesn't contain any slashes.
Reported by Paweł Forysiuk.
|
|
|
|
|
| |
It's not generated, and having it included removes it during
maintainer-clean so you have to retrieve it from the repo to build.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This commit fixes crash which occurs in Firefox, Thunderbird and Inkscape
during printing. This crash was caused because of wrong handling of Custom
CUPS options. (#543520)
|
|
|
|
| |
Apply patch from Paul Davis which implements this missing function.
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=665955
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When calling gtk_window_present(), gdk_win32_window_raise did not
actually raise the window anymore. Replacing BringWindowToTop() with
SetForegroundWindow() fixes this.
During testing, we also discovered that sometimes SetForeGroundWindow()
will (correctly) refuse to raise the window and fail(for example: sometimes
when dragging a different application at the time of a gtk_window_present()
call). To prevent a GdkWarning from being produced, usage of the API_CALL
macro has been removed for this case.
Additional goodies of SetForeGroundWindow:
- it brings the window to the front when the process owning the
window to raise is the foreground process (for example when
gtk_window_present is called from a GtkStatusIcon's activate
signal handler)
- it limits itself to flashing the task bar button associated
with the window if the process owning the window to raise
is *not* the foreground process (for example when gtk_window_present
is called from a g_timeout_add callback function)
https://bugzilla.gnome.org/show_bug.cgi?id=665760
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Modules would leak if they were specified twice in the same command,
so ie this would leak:
GTK_MODULES=gail,gail
|
|
|
|
|
| |
This way, we don't use the wrong module. In particular we don't screw up
refcounts that lead to crashes later on.
|