AuroraMiddleware/gtk2
1
0
Fork 0
forked from AuroraMiddleware/gtk
Code Issues Pull Requests Projects Releases Wiki Activity
53,643 Commits 969 Branches 749 Tags 504 MiB
4bbda548b7
Commit Graph

29881 Commits

Author SHA1 Message Date
Matthias Clasen
4bbda548b7 menushell: Stop using ::grab-broken 
The event-specific signals are going away. Just use ::event here.
 2018-01-16 14:14:10 -05:00
Matthias Clasen
fa07fe2124 notebook: some cleanup 2018-01-16 14:14:10 -05:00
Matthias Clasen
af8bf498e9 notebook: Use a motion event controller 
This lets us avoid the ::motion-notify-event handler.
 2018-01-16 14:14:10 -05:00
Matthias Clasen
7046463b88 textview: Use a motion event controller 
This lets us replace the ::motion-notify-event handler.
 2018-01-16 14:14:10 -05:00
Matthias Clasen
f594807c0a Drop ::enter/leave-notify-event 
These signals are no longer used in GTK+ and have a (not quite
perfect yet) replacement with GtkEventControllerMotion.

If you need to catch the raw events, the generic ::event
signal still works.
 2018-01-16 14:14:10 -05:00
Matthias Clasen
06605d54f2 menu: Use a motion event controller 
This lets us replace the ::enter/leave-notify-event handlers.
Not that there is a FIXME here - we currently can't get the
crossing mode from the event controller, so we have to fall
back to gtk_get_current_event().
 2018-01-16 14:14:10 -05:00
Matthias Clasen
6acf276a1a menuitem: Use a motion event controller 
This lets us replace the ::enter/leave-notify-event handlers.
Not that there is a FIXME here - we currently can't get the
crossing mode from the event controller, so we have to fall
back to gtk_get_current_event().
 2018-01-16 14:14:10 -05:00
Matthias Clasen
118424bd93 iconview: Use a motion event controller 
This can replace ::motion-notify-event and ::leave-notify-event.
 2018-01-16 14:14:10 -05:00
Matthias Clasen
ab4f4fb045 scrolled window: Use a motion event controller 
This lets use replace one of the last uses of ::leave-notify-event.
 2018-01-16 14:14:10 -05:00
Matthias Clasen
9ceafd7c38 entry completion: Drop initial selection avoidance 
This is a minor thing, and it is hard to recreate
with event controllers, so drop it for now.
 2018-01-16 14:14:10 -05:00
Matthias Clasen
a2a80f8a15 treeview: Use a motion event controller 
This replaces handlers for ::enter/leave/motion-notify-event.
 2018-01-16 14:14:10 -05:00
Matthias Clasen
cf9074a2e9 Add x/y to GtkEventControllerMotion::enter 
We have this information available in enter events,
and having it in the controller signal as well makes
porting easier.

Update existing users.
 2018-01-16 14:14:10 -05:00
Matthias Clasen
a9d468a4c8 Drop ::configure-event 
This signal is unused in GTK+ and configure events are handled
internally by GtkWindow.

If you need to catch configure events, the generic ::event
signal still works.
 2018-01-16 14:14:10 -05:00
Matthias Clasen
59572e5fcf window: Stop using ::configure-event 
We already have a generic ::event handler that we
can just press into service for this.
 2018-01-16 14:14:10 -05:00
Matthias Clasen
fa885f437c Drop ::touch-event 
This signal is not used in GTK+, and has a suitable
replacement with GtkGesture and its subclasses.

If you need to catch the raw touch events, the generic ::event
signal still works, too.
 2018-01-16 14:14:10 -05:00
Matthias Clasen
47712a826b Drop ::scroll-event 
This signal is not used in GTK+, and has a suitable
replacement with GtkEventControllerScroll.

If you need to catch these events, the generic ::event
signal still works, too.
 2018-01-16 14:14:10 -05:00
Matthias Clasen
e93c2517e6 Drop ::proximity-in-event and ::proximity-out-event 
These are unused in GTK+, and are not very common.
If you need to catch these events, the generic ::event
signal still works.
 2018-01-16 14:14:09 -05:00
Matthias Clasen
fd2a3b602f Drop ::map-event and ::unmap-event 
These are unused in GTK+, and are not very common.
If you need to catch these events, the generic ::event
signal still works.
 2018-01-16 14:14:09 -05:00
Matthias Clasen
ab53142c0f window: Stop using ::map-event 
Use ::event here, since we want to drop the event-specific
signals, and we already have a handler for the generic signal.
 2018-01-16 14:14:09 -05:00
Matthias Clasen
1e0ae936fe widget: Stop using ::map-event 
Use ::event here, since we want to drop the event-specific
signals.
 2018-01-16 14:14:09 -05:00
Matthias Clasen
7b581ca096 Drop GtkWidget::destroy-event 
This signal is unused in GTK+, and is documented as
'hard to ever get', so there's no good reason for
keeping it.
 2018-01-16 14:14:09 -05:00
Matthias Clasen
2b52b4be5d Drop GtkWidget::delete-event 
Nobody is using this signal anymore, and ::delete is there
for the few places where it is needed.
 2018-01-16 14:14:09 -05:00
Matthias Clasen
a739ee6905 Replace GtkWidget::delete-event by GtkWindow::close-request 
The event is not useful at all, so we are better off
with a signal that doesn't have it, and it is only
relevant on toplevel windows, so we don't need it on
GtkWidget.

With this commit, delete events no longer go through the
::event, ::delete-event, ::event-after widget signals,
but just cause the ::close-request signal on GtkWindow to be
emitted.
 2018-01-16 14:14:09 -05:00
Matthias Clasen
76fea5c5fa treeview: Don't handle ::delete-event 
I don't think there is a way to get a delete event
on this popup - there's no window decorations, no close
button, etc. So no need to handle ::delete-event.
 2018-01-16 14:14:09 -05:00
Matthias Clasen
7e491fd3fc font chooser: Stop using ::scroll-event 
We have an event controller for this purpose now.
 2018-01-16 14:14:09 -05:00
Matthias Clasen
d2edcf489b treeview: Use a scroll event controller 
This is the recommended way to deal with scroll events
now.
 2018-01-16 14:14:09 -05:00
Matthias Clasen
4923da3550 Drop gtk_true and gtk_false 
These functions are entirely trivial, their documentation
is much longer than their implementation, and it contains
an example that is annotated as "don't do this"...
 2018-01-16 14:14:09 -05:00
Matthias Clasen
75271c44c2 inspector: Stop using ::delete-event signal 
We can just use GtkWindow::hide-on-close instead.
 2018-01-16 14:14:09 -05:00
Matthias Clasen
e7bd666711 treeview: Stop using gtk_true 2018-01-16 14:14:09 -05:00
Matthias Clasen
c4513a6737 dialog: Stop using the ::delete-event signal 
We can achieve the desired result with a class handler
and the ::hide-on-close property.
 2018-01-16 14:14:09 -05:00
Matthias Clasen
d6e92cd984 file chooser native: Stop connecting to ::delete-event 
We can just use GtkWindow::hide-on-close.
 2018-01-16 14:14:09 -05:00
Matthias Clasen
d0f071aae9 file chooser button: Stop connecting to ::delete-event 
We can just use GtkWindow::hide-on-close.
 2018-01-16 14:14:09 -05:00
Matthias Clasen
a1b6bf19c1 applicationwindow: Stop connecting to ::delete-event 
We can just use GtkWindow::hide-on-close.
 2018-01-16 14:14:09 -05:00
Matthias Clasen
59878f281f about dialog: Stop connecting to ::delete-event 
We can just use GtkWindow::hide-on-close.
 2018-01-16 14:14:09 -05:00
Matthias Clasen
c86e8d0e60 color button: Stop connecting to ::delete-event 
We can just use GtkWindow::hide-on-close.
 2018-01-16 14:14:09 -05:00
Matthias Clasen
b919c3348f font button: Use GtkWindow::hide-on-close 
Instead of the ::delete-event signal.
 2018-01-16 14:14:09 -05:00
Matthias Clasen
c04f192113 window: Add a hide-on-close property 
This lets us avoid ::delete-event signal handlers for just
this purpose.
 2018-01-16 14:14:09 -05:00
Matthias Clasen
370d666406 inspector: Avoid a critical 
I forgot to initialized the text field when I added
it back.
 2018-01-15 08:01:54 -05:00
Matthias Clasen
978c597e94 inspector: Some logging support 
Add a way to toggle debug output on and off
from the inspector. For now, we don't add a
log viewer here, since that has the risk of
deadlock until we've the logging completely
separated by display, and also requires us
to install a log writer function, which
libraries are not supposed to do.
 2018-01-14 17:05:04 -05:00
Matthias Clasen
f9100719bd inspector: Turn off gsk debugging 
We don't want debug spew from the renderer that
is used for the inspector window, so turn it off.
 2018-01-14 17:05:04 -05:00
Matthias Clasen
c3215de005 gtk Use per-renderer flags for node names 
We are moving to per-renderer flags, so lets check them here.
 2018-01-14 17:05:04 -05:00
Matthias Clasen
1d2606dc94 Drop the cairo-recording debug flag 
It is not very useful. The cairo-image option on the
other hand is has been useful in tracking down problems
in the past, so we'll keep it.
 2018-01-14 17:05:04 -05:00
Matthias Clasen
08dc2cd6a8 Drop the gl-always debug option 
This doesn't seem very useful.
 2018-01-14 17:05:04 -05:00
Matthias Clasen
e151058dff Make gdk logging per-display 
As far as possible, use per-display debug flags.

This will minimize the debug spew that we get from
the inspector if it is running on a separate display.
 2018-01-14 17:05:04 -05:00
Matthias Clasen
c5fc841285 gdk: Reorganize env vars 
Drop GDK_GL, GDK_VULKAN and GDK_RENDERING_MODE.
Merge the useful bits into GDK_DEBUG.
Drop unused debug flags (CURSOR).
 2018-01-14 17:05:04 -05:00
Matthias Clasen
af7f695068 Make geometry logging per-display 
Use the new macro to do this.
 2018-01-14 17:05:04 -05:00
Matthias Clasen
461d05f643 icon theme: Make logging per-display 
As far as possible, for now. This needs some more
work to cover all locations.
 2018-01-14 17:05:04 -05:00
Matthias Clasen
22e59ecd28 gtk: add a per-display log macro 
This makes the conversion easier.
 2018-01-14 17:05:04 -05:00
Daniel Boles
db6127a118 HeaderBar: Explain use in conjunction w/ GtkWindow 
After hinting how good GtkHeaderBar is for GtkWindow, let’s link to
the latter and indicate how users can make the two work together.
 2018-01-13 20:06:20 +00:00
Daniel Boles
e0f69353bb Window: Mention GtkHeaderBar in set_titlebar() doc 
This is the typical thing passed here and what most users want, so we
should mention it here, rather than requiring users to figure it out.
 2018-01-13 20:06:20 +00:00