AuroraMiddleware/gtk
1
0
Fork 1
mirror of https://gitlab.gnome.org/GNOME/gtk.git synced 2024-11-10 10:50:10 +00:00
Code Issues Projects Releases Wiki Activity
52,333 Commits 1,224 Branches 805 Tags 575 MiB
9151e0b9f5
Commit Graph

52333 Commits

This Branch
This Branch
All Branches
Author SHA1 Message Date
Benjamin Otte
9151e0b9f5 stylecontext: Port to use display instead of screen 2017-10-31 03:05:54 +01:00
Benjamin Otte
a2e625692e gtk-demo: Remove calls to gtk_style_context_reset_widgets() 
Those calls have been unneeded for a long time - since we gained the
changed signal on the StyleProvider in fact.
 2017-10-31 03:05:54 +01:00
Matthias Clasen
5c2e254f65 Drop gdk_pango_context_get 
This is a trivial convenience api, and it is not used in gtk.
 2017-10-30 21:36:37 -04:00
Matthias Clasen
ffb3bc438e tests: Stop using gdk_pango_context_get. 
We can just as well get the display ourselves.
 2017-10-30 21:35:48 -04:00
Matthias Clasen
1f114b1257 Drop gdk_pango_context_get_for_screen 
GdkScreen is going away, and this api is unused in gtk.
 2017-10-30 21:29:48 -04:00
Benjamin Otte
cb0c7d6cf3 immulticontext: Remove unused variable 2017-10-31 00:44:35 +01:00
Benjamin Otte
44614394e6 widget: Turn screen-changed signal into display-changed 2017-10-31 00:43:11 +01:00
Benjamin Otte
59cfd56365 settings: Don't store the screen in the settings object 
Screens are going away.

Code that still needs the screen just gets it from the display.
 2017-10-31 00:42:32 +01:00
Matthias Clasen
9e5f4f94b3 immulticontext: Avoid GdkScreen api 
No need for it here either.
 2017-10-30 19:30:29 -04:00
Matthias Clasen
297889e080 immodule: Avoid GdkScreen api 
Another place where it is not needed.
 2017-10-30 19:27:36 -04:00
Matthias Clasen
24903e3fab modules: Avoid GdkScreen api 
No need for this here either.
 2017-10-30 19:19:38 -04:00
Matthias Clasen
0cd864283f assistant: Avoid GdkScreen api 
There is no need at all here to use gtk_settings_get_for_screen.
 2017-10-30 19:19:38 -04:00
Matthias Clasen
a1a5f556cb Some documentation updates 
Document gtk_settings_get_for_display instead of for_screen.
 2017-10-30 18:59:41 -04:00
Matthias Clasen
154117218c Drop gdk_screen_get_setting 
It has been replaced by gdk_display_get_setting.
 2017-10-30 17:03:09 -04:00
Matthias Clasen
d9809df8ce wayland: Stop using gdk_screen_get_setting 
Use gdk_display_get_setting instead.
 2017-10-30 17:01:46 -04:00
Matthias Clasen
51ba0b41a2 x11: Stop using gdk_screen_get_setting 
Use gdk_display_get_setting instead.
 2017-10-30 17:01:18 -04:00
Matthias Clasen
378c7648ba Drop the GdkScreen get_setting vfunc 
It is unused.
 2017-10-30 16:53:17 -04:00
Matthias Clasen
42d2b50515 x11: Don't set the GdkScreen get_setting vfunc 
We are not using it anymore.
 2017-10-30 16:52:56 -04:00
Matthias Clasen
2a4da2cfcd wayland: Don't set the GdkScreen get_setting vfunc 
We are not using it anymore.
 2017-10-30 16:52:39 -04:00
Matthias Clasen
2a3e7e93d3 broadway: Don't set the GdkScreen get_setting vfunc 
We are not using it anymore.
 2017-10-30 16:52:21 -04:00
Matthias Clasen
dea277520f quartz: Don't set the GdkScreen get_setting vfunc 
We are not using it anymore.
 2017-10-30 16:51:59 -04:00
Matthias Clasen
96f1e83877 mir: Don't set the GdkScreen get_setting vfunc 
We don't use it anymore.
 2017-10-30 16:51:38 -04:00
Matthias Clasen
e821c2fc2f gtk: Avoid using gdk_screen_get_setting 
We can get the setting from the display instead.
 2017-10-30 16:51:20 -04:00
Matthias Clasen
f9cc7ca140 Add gtk_settings_get_for_display 
This will help us avoiding screens in many places.
 2017-10-30 16:50:14 -04:00
Matthias Clasen
6dbb1e20a6 Stop using the GdkScreen get_setting vfunc 
We can now call the GdkDisplay implementation instead.
 2017-10-30 16:45:36 -04:00
Matthias Clasen
f9dacd6de0 use the GdkDisplay get_setting vfunc 
Instead of calling the GdkScreen implementation, use our
own vfunc now.
 2017-10-30 16:44:47 -04:00
Matthias Clasen
19157c5bf4 x11: Implement the GdkDisplay get_setting vfunc 
Just call the GdkScreen vfunc.
 2017-10-30 16:44:18 -04:00
Matthias Clasen
4ffe9ca70c wayland: Implement the GdkDisplay get_setting vfunc 
Just call the GdkScreen vfunc.
 2017-10-30 16:43:50 -04:00
Matthias Clasen
729aeef6ab broadway: Implement the GdkDisplay get_setting vfunc 
This is just a trivial implementation.
 2017-10-30 16:43:13 -04:00
Matthias Clasen
c63c672ba8 quartz: Implement the GdkDisplay get_setting vfunc 
Just call the GdkScreen vfunc.
 2017-10-30 16:42:49 -04:00
Matthias Clasen
a9ea420b65 mir: Implement the GdkDisplay get_setting vfunc 
Just call the corresponding screen vfunc.
 2017-10-30 16:41:59 -04:00
Matthias Clasen
f2055bfb7b gdk: Add a get_setting vfunc to GdkDisplay 
This will eventually replace the GdkScreen vfunc of the
same name.
 2017-10-30 16:39:49 -04:00
Matthias Clasen
a518072e87 Remove GdkScreen api usage 
Use GdkDisplay equivalents where they exist.
 2017-10-30 16:06:42 -04:00
Matthias Clasen
1f22c6532e Store the display inside GtkSettings 
This is a step towards dropping GdkScreen.
 2017-10-30 15:56:03 -04:00
Matthias Clasen
209f24f962 Remove gdk_setting_get 
This is a minor convenience api, and it is unused.
 2017-10-30 15:31:02 -04:00
Matthias Clasen
e99687194a Forgotten files 
Clean up the setting event from headers and docs too.
 2017-10-30 10:08:32 -04:00
Matthias Clasen
10ba84a6a9 gdk: Drop settings events 
We are not emitting these events anymore, so lets remove them
from the api. The GdkSettingAction enum is moved to xsettings-client.c
where its only use remains.
 2017-10-30 09:49:02 -04:00
Matthias Clasen
7e8e4dcf76 x11: Stop emitting settings events 
Not needed anymore.
 2017-10-30 09:49:02 -04:00
Matthias Clasen
5d4c979425 wayland: Stop emitting setting events 
Not needed anymore.
 2017-10-30 09:49:02 -04:00
Matthias Clasen
627c0ae549 quartz: Stop emitting setting events 
Not needed anymore.
 2017-10-30 09:49:02 -04:00
Matthias Clasen
d3e45cf087 mir: Stop emitting setting events 
Not needed anymore.
 2017-10-30 09:49:02 -04:00
Matthias Clasen
2926669a9b gtk: Stop handling settings events 
We don't need this anymore, now that we use the ::setting-changed
signal.
 2017-10-30 09:48:51 -04:00
Matthias Clasen
a8aff6ef8f gtk: Connect to GdkDisplay::setting-changed 
We still handle the setting event, for now.
That will be removed in a future commit.
 2017-10-30 09:29:54 -04:00
Matthias Clasen
8686526b4a x11: Emit GdkDisplay::setting-changed 
We still generate the event too.
That will be removed in a future commit.
 2017-10-30 09:29:09 -04:00
Matthias Clasen
3c0614994f wayland: Emit GdkDisplay::setting-changed 
We still generate the event too.
That will be removed in a future commit.
 2017-10-30 09:28:29 -04:00
Matthias Clasen
36a94b49c7 quartz: Emit GdkDisplay::setting-changed 
We still generate the event too.
That will be removed in a future commit.
 2017-10-30 09:27:59 -04:00
Matthias Clasen
bb6c8a475f mir: Emit GdkDisplay::setting-changed 
We still generate the event too.
That will be removed in a future commit.
 2017-10-30 09:23:16 -04:00
Matthias Clasen
61d13b0f14 gdk: Add settings api to GdkDisplay 
This commit adds gdk_display_get_setting and a ::setting-changed
signal, which will replace the settings event we use now. Note
that I've done away with the GdkSettingAction argument that the
event has, since we are not using it at all.
 2017-10-30 09:21:47 -04:00
Lukas K
15491cf6e4 make GDK_DEBUG=opengl work on win32 2017-10-30 14:39:55 +08:00
Chun-wei Fan
64a489adbf input/IME: Defer the emit of the "commit" signal 
On Windows, when IME is used, each keystroke results in the
WM_IME_COMPOSITION event being sent first.  This means that in our case
when one decides on to accept the input that is in the preedit buffer,
we first get from Windows the WM_IME_COMPOSITION event
(where we emit the commit signal), followed by the WM_IME_ENDCOMPOSITION
event (where we emit the pair of preedit-changed and preedit-end
signals).

Since commit f11f989 (GtkEntry: Remove recompute idle), we do the input
recomputation directly, this will cause a pair of "Pango-WARNING:
Assertion failed: (index >= 0 && index <= layout->length)" being shown,
as gtkentry.c's priv->preedit_length and priv->preedit_cursor was unable
to be reset to 0 in time as a result of the recomputation triggered by
the commit being done before the reset of priv->preedit_length and
priv->preedit_cursor (which are no longer valid as we essentially say
that we are done with the preedit buffer).

As we could only acquire the final string that was entered in this
preedit session when we handle the WM_IME_COMPOSITION event, fix this by
saving up the final string we acquire from Windows IME in UTF-8 when we
handle the WM_IME_COMPOSITION event from Windows, and emit the commit
signal with that string after we emit the preedit-changed and
preedit-end signals when we handle the WM_IME_ENDCOMPOSITION event from
Windows, which comes afterwards.

Also fix the formatting of the code around the parts of the files that
was changed.

https://bugzilla.gnome.org/show_bug.cgi?id=787142
 2017-10-30 14:33:06 +08:00