AuroraMiddleware/gtk
1
0
Fork 1
mirror of https://gitlab.gnome.org/GNOME/gtk.git synced 2024-11-14 20:51:07 +00:00
Code Issues Projects Releases Wiki Activity
53,239 Commits 1,228 Branches 805 Tags 590 MiB
ddb77d6c9b
Commit Graph

53239 Commits

This Branch
This Branch
All Branches
Author SHA1 Message Date
Matthias Clasen
1012bbeecf Add gdk_display_get_keymap 
This is just a better name for gdk_keymap_get_for_display.
 2017-12-15 06:53:13 -05:00
Matthias Clasen
fd85ff0c7a Drop gdk_keymap_get_default() 
It is better to use the explicit keymap getter - the
default display may not even use the current gdk backend.
 2017-12-14 23:57:54 -05:00
Matthias Clasen
9194ee4973 gdk: Drop GDK_DAMAGE 
We haven't been generating events of this type
since we dropped offscreen windows.
 2017-12-14 23:35:08 -05:00
Matthias Clasen
65fc43a1f3 Drop GDK_CLIENT_EVENT 
We never generate events of this type, so no need
to carry it around.
 2017-12-14 22:55:03 -05:00
Matthias Clasen
8d42ab6b91 gdk: Remove explicit event type numbering 
The numeric values of event types are irrelevant,
so we don't need to declare them explicitly.
 2017-12-14 22:43:53 -05:00
Matthias Clasen
bcf570cc16 Move code around 
gdk_window_set_state is now an ordinary (private) setter,
so it should live in gdkwindow.c.
 2017-12-14 22:35:27 -05:00
Matthias Clasen
11a946df39 gdk: Drop GdkEventWindowState 
No longer generate this event. Instead, emit change
notification for GdkWindow::state.
 2017-12-14 22:24:06 -05:00
Matthias Clasen
a4a2ecb21a widget: Remove the ::window-state-event signal 
We no longer use this signal, so remove it.
 2017-12-14 22:24:06 -05:00
Matthias Clasen
0313b8f0bc gtk: Stop handling GdkEventWindowState 
These events have been superseded by GdkWindow::state.
 2017-12-14 22:24:06 -05:00
Matthias Clasen
8476fc3fb0 menu: Stop using GdkEventWindowState 
These events are going away.
 2017-12-14 22:24:06 -05:00
Matthias Clasen
c1f9d7cb16 a11y: Stop using GdkEventWindowState 
These events are going way.
 2017-12-14 22:24:06 -05:00
Matthias Clasen
40d57ff884 headerbar: Stop using GdkEventWindowState 
Use GdkWindow::state instead - the event is going away.
 2017-12-14 22:24:06 -05:00
Matthias Clasen
ce251133c0 gtk-demo: Stop using GdkEventWindowState 
Use GdkWindow::state instead - the event is going away.
 2017-12-14 22:24:06 -05:00
Matthias Clasen
2c267a3cf1 testgtk: Stop using GdkEventWindowState 
Use GdkWindow::state instead - the event is going away.
 2017-12-14 22:24:06 -05:00
Matthias Clasen
1e1904a9b8 gtk: Stop using GdkEventWindowState 
We can instead use the new GdkWindow::state property
change notification. The event is going away.
 2017-12-14 22:24:06 -05:00
Matthias Clasen
e5b1867118 gdk: Add a GdkWindow::state property 
This will eventually replace the window state event.
 2017-12-14 22:24:06 -05:00
Daniel Boles
fe20fc3128 FileChooser: Update set_local_only() doc’s default 
The property now defaults to FALSE, but the setter doc didn’t reflect it

While here, add a missing apostrophe too.

https://bugzilla.gnome.org/show_bug.cgi?id=791176
 2017-12-14 15:36:43 +00:00
Benjamin Otte
84431ab927 x11: Remove GdkAtom usage from dnd code 
Use strings instead.
 2017-12-14 13:46:37 +01:00
Benjamin Otte
5d70bbf4c4 display: Remove leftover old clipboard APIs 2017-12-14 13:35:32 +01:00
Krzesimir Nowak
5a0fb278d1 x11: Fix erroneous & to be && 2017-12-14 13:35:32 +01:00
Benjamin Otte
920259c250 x11: Get rid of default Atom converters 
No, using the default Wayland display is not okay to query Atoms.
 2017-12-14 13:35:32 +01:00
Benjamin Otte
52b1a46549 device: Make axis label a regular string 
Atoms are about to die.
 2017-12-14 13:35:32 +01:00
Stas Solovey
b1f11464b6 Update Russian translation 
(cherry picked from commit d69f998c26)
 2017-12-14 09:58:21 +00:00
Matthias Clasen
75dd3315e6 Drop atom apis from the docs 
These no longer exist.
 2017-12-13 23:47:51 -05:00
Matthias Clasen
84eaf3da7d Drop atom-related cast macros 
These don't really add anything, just drop them.
 2017-12-13 23:47:02 -05:00
Matthias Clasen
54a6273191 Drop gdk_atom_intern 
Atoms are just interned strings now, so we can just
use g_intern_string.
 2017-12-13 23:39:03 -05:00
Matthias Clasen
4c083c1ed4 Drop gdk_atom_name 
Since atoms are just interned strings now, we can just
cast them to const char * where needed.
 2017-12-13 23:26:23 -05:00
Matthias Clasen
e3e9bf4bea Remove no-longer-used signals 
GtkWidget::selection-get and ::selection-received are no
longer used, so get rid of them.
 2017-12-13 22:53:50 -05:00
Benjamin Otte
b49a9b9933 dnd: Remove gdk_drag_get_selection() 
Without selections, drags can't have them either.

Also included is removing the selection from GtkSelectionData.

Includes a bunch of crude cleanups to Wayland code that no longer has to
care about selection atoms.
 2017-12-14 04:39:22 +01:00
Benjamin Otte
65fcff87b2 gdk: Remove ability to request selection notifications 
Without selections, that's kinda pointless.
 2017-12-14 04:20:48 +01:00
Benjamin Otte
f2bb2024c8 gdk: Remove properties 
They are not used anymore.

Gone with them are PropertyNotify events.
 2017-12-14 03:05:34 +01:00
Benjamin Otte
82aa0eacb2 broadway: Make compile after GdkEvent objectification 2017-12-14 03:05:34 +01:00
Benjamin Otte
38d8fa0b6a gesture: Fix gcc constness warning 2017-12-14 03:05:34 +01:00
Benjamin Otte
d7f34874ab x11: Make unsetting transient-for work 
... and just unset it from GtkWindow instead of fiddling with
properties.
 2017-12-14 03:05:34 +01:00
Benjamin Otte
a4b42f0b73 gdk: Remove selection defines 
And with it, remove the selections section from the docs.

So selections are gone for good now.
 2017-12-14 03:05:34 +01:00
Georges Basile Stavracas Neto
8993a51893 vulkan: Destroy buffer before releasing associate memory 
Exact same issue as the previous commit.
 2017-12-13 23:14:58 -02:00
Georges Basile Stavracas Neto
147a455171 vulkan: Destroy image before releasing associate memory 
VkImage contains a reference to the VkDeviceMemory and, because
the current code frees the VkDeviceMemory before destroying the
VkImage that references it, a warning is triggered by the validation
layers.

This is not critical, since we release both resources at the same
place. But the warning triggered by the validation layers sums up
adding 1 MB per second of extra debug logging, making the debugging
process much more painful.

This commit simply swaps the destruction order, and destroys the
VkImage first, then the now unused VkDeviceMemory.
 2017-12-13 22:49:16 -02:00
Piotr Drąg
192bdae280 Update POTFILES.in 2017-12-14 01:15:17 +01:00
Carlos Garnacho
2f65a2f5cc gdk: Make gdk_display_peek_event() Return a reference to the event 
No need to copy it.
 2017-12-14 01:05:48 +01:00
Carlos Garnacho
332b640cd3 gtk: Make gtk_get_current_event() return a reference 
All callers in gtk seem to be ok with it, and it makes sense if
we are dealing with events as "static after delivered".
 2017-12-14 01:05:48 +01:00
Carlos Garnacho
ee178947d7 gtk: Avoid some event copies 
Those places can do with an extra reference.
 2017-12-14 01:05:48 +01:00
Carlos Garnacho
d491e49fd6 gtk: s/gdk_event_free/g_object_unref/ 2017-12-14 01:05:48 +01:00
Carlos Garnacho
b03d3fb268 gdk/wayland: s/gdk_event_free/g_object_unref/ 2017-12-14 01:05:48 +01:00
Carlos Garnacho
3021edc38d gdk/x11: s/gdk_event_free/g_object_unref/ 2017-12-14 01:05:48 +01:00
Carlos Garnacho
f79ac6d30b gdk: Remove gdk_window_[gs]et_event_compression() 
Motion compression is now the unmodifiable default, callers may
call gdk_event_get_motion_history() to check the uncoalesced
motion history.
 2017-12-14 01:05:48 +01:00
Carlos Garnacho
47f04afa48 gtk: Remove CONSTRUCT_ONLY flag from GtkEventControllerScroll::flags 
There is a gtk_event_controller_scroll_set_flags() call that's meant
to be called after construction (eg. due to scrolledwindow relayouts
hiding/showing scrollbars). The property shouldn't be construct-only
for consistence.
 2017-12-14 01:05:48 +01:00
Carlos Garnacho
ea216accd7 gdk: Implement motion history as motion event data 
In the motion compression phase the coalesced events will be saved
as a GdkTimeCoord on the motion event that shall be delivered.

For simplicity (and because history doesn't make much sense otherwise)
event history is only recorded while there are buttons pressed, this
also tidily ensures that those coalesced events would have the same
target widget on the gtk side than the delivered one, because of
implicit grabs.
 2017-12-14 01:05:48 +01:00
Carlos Garnacho
a040ed55cc gdk: Keep reference on tools from motion/button events. 2017-12-14 01:05:48 +01:00
Carlos Garnacho
8c9231dbb4 gdk: Move additional code in gdk_event_new() to GdkEvent::constructed 
Now that the type is a construct only property, we can initialize the
event fields properly here.
 2017-12-14 01:05:48 +01:00
Carlos Garnacho
5ee1d4893a gdk: Make GdkEvent type a construct only property 
So it must be set at the time of doing g_object_new().
 2017-12-14 01:05:48 +01:00