| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
https://gitlab.gnome.org/GNOME/gtk/issues/1069
|
| |
|
|
|
|
|
|
|
| |
This is the updates to the Visual Studio 2008 projects to generate
gtk/gtktypefuncs.c using the preprocessor and the gentypefuncs.py that
was adapted from master.
Unfortunately we could not clean up the projects as we did for the 201x
ones due to the differences in project file format.
|
| |
|
|
|
|
| |
Combine repetitive parts, and unify using $(PythonDir) for all builds,
which the paths set in the property sheets are now based on the Visual
Studio version and platform combination.
|
| |
|
|
|
|
| |
Not that it will make a difference, but to be consistent with the
autotools builds. Include gtkx.h instead of gtk.h when we generate the
source to feed to the preprocessor.
|
| |
|
|
|
|
|
| |
We now need to generate gtktypefuncs.c by ourselves, so modify the
gentypefuncs.py script from master, and add a custom build step in the
projects to generate gtktypefuncs.c. The custom build step for the 2008
projects will be added later.
|
| |\
| |
| |
| |
| | |
wayland: Fix restarting cursor animation
See merge request GNOME/gtk!150
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When an animated cursor was set and the previous cursor animation delay
happened to be the same, we wouldn't restart the animation timeout and
just return G_SOURCE_CONTINUE assuming the timer would continue. This
assumption is however only valid if the function was called from the
timeout, which is not the case.
Instead also arm the timer also if there is no previous timer active.
|
| | |
| |
| |
| |
| | |
We now need the generated sources to be included explicitly in the list
so that they get listed in the project files to be built.
|
| |/
|
|
|
|
| |
It seems that CoreText is internally calibrated for this, see
https://bugzilla.gnome.org/show_bug.cgi?id=787867 for a detailed
discussion.
|
| |
|
|
|
|
| |
So gcc stops complaining about unnecessary parenthesis.
Closes #1059
|
| |
|
|
|
|
|
|
|
| |
In scroll_event(), there is no need to check whether we are realized
before emitting ::change-value, as we must be when receiving an event.
Git-formatted/rebased/cleaned up by Daniel Boles <dboles.src@gmail.com>
Close https://gitlab.gnome.org/GNOME/gtk/issues/292
|
| |
|
|
|
|
|
| |
• #include <math.h> for the new uses of floor()
• Move the new ints and popdown_data into the scopes where they are used
• Don’t pointlessly init other ints to 0 as they always get reassigned
• Burninate gint
|
| |
|
|
|
|
|
|
|
|
| |
This issue was caused when mouse coordinates were changed to floating
point values in commit e8b38fedbd8961df4aaaa75b122a06ddc68e75f2.
This patch floors the event->x_root and event->y_root values when
setting the navigation region, so the previous behaviour is restored.
https://gitlab.gnome.org/GNOME/gtk/issues/450
|
| |
|
|
| |
This avoids black flicker on compositing WMs when a window is first shown.
|
| |
|
|
|
|
|
|
| |
Use g_str_match_string for better results.
cherry-pick of be2853e5deb60274e43352352de74dc458908fe2
https://gitlab.gnome.org/GNOME/gtk/issues/898
|
| |\
| |
| |
| |
| | |
wayland: Use dev/evdev/input.h on FreeBSD (GTK3)
See merge request GNOME/gtk!132
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The header linux/input.h used by GDK is specific to Linux. It is
possible to get a few Linux headers on FreeBSD by installing v4l_compat,
but it is usually better to use the one shipped with FreeBSD.
We prefer dev/evdev/input.h to linux/input.h here, so it will always use
dev/evdev/input.h on FreeBSD regardless of v4l_compat.
https://svnweb.freebsd.org/changeset/ports/465644
|
| |/ |
|
| |\
| |
| |
| |
| |
| |
| | |
'gtk-3-22'
Resolve "GtkTextView accesses already disposed object" in 3.22
See merge request GNOME/gtk!110
|
| | |
| |
| |
| |
| |
| |
| | |
Instead of asking of TextMark for its buffer,
let's reference also the buffer in the SelectionData.
Closes #169
|
| |\ \
| | |
| | |
| | |
| | | |
gdk: do not deactivate window on keyboard grabs
See merge request GNOME/gtk!127
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When pressing e.g. a window manager shortcut, which acquires keyboard grab,
Xorg would send FocusOut NotifyGrab then FocusIn NotifyUngrab. Currently
gdk would then deactivate the current surface, which makes accessibility
screen readers think that we have switched to a non-accessible application
and came back again, and thus reannounce the application frame etc. which we
don't want when e.g. just raising volume.
And actually, receiving FocusOut NotifyGrab does not mean losing the
X focus, it only means an application aqcuired a grab, i.e. it is
temporarily stealing keyboard events. On Wayland, this isn't even
notified actually.
This commit makes gdk only deactivate surfaces when there was an actual
focus switch to another window, as determined by has_focus_window (instead
of just has_focus), which happens either normally through FocusOut with
NotifyNormal, or during grabs through FocusOut with NotifyWhileGrabbed.
Fixes #85
(cherry picked from commit 01455399e83a3dbafb0cdc6e12c7003b2f472a40)
|
| | |
| |
| |
| | |
Another instance of a check needed for gdk_win32_selection_add_targets().
|
| | |
| |
| |
| | |
gdk_win32_selection_add_targets() is for W32 displays only.
|
| | |
| |
| |
| |
| |
| | |
gdk_win32_keymap_check_compose() shouldn't be called for
non-W32 displays (i.e. when using broadway or other backends
that could be made to run on Windows).
|
| | |
| |
| |
| | |
This version also merges widgetbowl into fishbowl.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
to retreive paper size specific hard margins and use this
to set the hard margins in the print context.
(modified by Marek Kasik <mkasik@redhat.com>)
https://bugzilla.gnome.org/show_bug.cgi?id=686109
|
| | | |
|
| | |
| |
| |
| |
| | |
Instead of getting the model again but then forgetting to cast it to a
ListStore, just use the other variable store where we already did both.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The shortcuts inhibitors hash table is created when we create a
GdkWaylandWindow implementation for a GdkWindow, and it's destroyed once
we finalize the instance. The fake "root" window we create for the
Wayland display does not have a backing native window, so the shortcuts
inhibitors hash table is set to NULL; this causes a critical error
message when calling g_hash_table_destroy() on it. The finalization of
the root window happens when we close a display connection.
We should use g_clear_pointer(), instead, as it's NULL safe.
Without this change, the displayclose test fails, as all warnings are
considered fatal.
|
| | |
| |
| |
| |
| |
| | |
We expect these files to be regenerated even when building GTK+ from a
release tarball, so there's no point in distributing them if they are
going to be ignored.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Epoxy 1.4 has new ad hoc API that we can use to check whether GLX is
available on the current system.
If we didn't use this API, we'd have to manually dlopen libGL (or its
equivalent on different OSes) and check if it had GLX symbols; since
Epoxy already does all of this internally, we can simply ask it instead.
https://bugzilla.gnome.org/show_bug.cgi?id=775279
(cherry picked from commit 02eb344950547c66a9096094f271b98e94614fcb)
Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
|
| | |
| |
| |
| |
| |
| |
| | |
We're going to use API introduced in libepoxy 1.4 to check for GLX
availability.
https://bugzilla.gnome.org/show_bug.cgi?id=775279
|
| | |
| |
| |
| | |
bah.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
.linked assumes the container is a GtkBox, which is documented as never
flipping children in RTL, so :first-child is always the left child, etc.
GtkBox does that by reordering its CSS nodes when the direction changes.
But most widgets don’t do that, so :first|last-child are 1st/last ADDED
and swap sides in RTL. GtkPathBar is so, and ignoring that in our themes
meant that in RTL, its left/right buttons got each other’s borders. Yuk!
This patch adds the groundwork for supporting widgets like that, via the
%linked_flippable placeholder, and applies that to override buttons in
filechooser .path-bar.linked > button
so that the correct borders get applied to those buttons when using RTL.
Note that I select only PathBars within a FileChooser because we also
have NautilusPathBar, which also uses widget.path-bar – but *does* flip
its nodes for RTL already, so letting that get affected broke it again!
https://bugzilla.gnome.org/show_bug.cgi?id=772817
|
| | |
| |
| |
| |
| |
| | |
This was missed (even before my recent patches).
https://gitlab.gnome.org/GNOME/gtk/issues/199
|
| | |
| |
| |
| |
| |
| |
| | |
Otherwise, we do stuff we shouldn't, as the failing pipeline showed:
https://gitlab.gnome.org/GNOME/gtk/pipelines/9431
https://gitlab.gnome.org/GNOME/gtk/issues/199
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
Otherwise, if the Popover is destroyed before the MenuButton, the latter
still had a non-NULL but invalid instance and tried to use it in dispose
https://gitlab.gnome.org/GNOME/gtk/issues/199
|
| | |
| |
| |
| | |
https://bugzilla.gnome.org/show_bug.cgi?id=786524
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
A user in #gtk+ was confused what to do instead of creating a Button via
gtk_button_new_from_stock(). Our docs could stand to be clearer on this
point; it only costs a few lines. So, link from that constructor* to the
GtkStock doc, and add a banner there telling folk they shouldn’t use it.
* not that most [of these][links] even work right now…
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
rather than being a requirement for using our selection APIs.
https://bugzilla.gnome.org/show_bug.cgi?id=791542
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Use g_signal_connect_data() instead of g_signal_connect_object()
to make sure the callback gets disconnected when the data object
is destroyed. This avoids problems in garbage-collected bindings.
https://bugzilla.gnome.org/show_bug.cgi?id=789215
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
The GVariant we are getting here might not be coming
from GTK+, but rather from some other source. Best to
be forgiving and deal with missing data without crashing.
This was causing the GTK+ portal backends to crash on
print requests from Qt.
|
| |\ \
| | |
| | |
| | |
| | | |
stack: protect set_visible_child_name from NULL stack
See merge request GNOME/gtk!117
|
| | | |
| | |
| | |
| | |
| | | |
Return with error if gtk_stack_set_visible_child_name is called
with NULL parameter
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Gtkplacesview finalization fixes
See merge request GNOME/gtk!119
(cherry picked from commit e30176a5228228f28f914d87120b9a650d0073b8)
f9452957 gtkplacesview: unset entry_pulse_timeout_id before removing it
4900c3eb gtkplacesview: disconnect from server list monitor changes on destroy
|
| | |
| |
| |
| | |
Close https://gitlab.gnome.org/GNOME/gtk/issues/193
|
