Trait gtk::prelude::EventBoxExt
source · [−]pub trait EventBoxExt: 'static {
fn is_above_child(&self) -> bool;
fn is_visible_window(&self) -> bool;
fn set_above_child(&self, above_child: bool);
fn set_visible_window(&self, visible_window: bool);
fn connect_above_child_notify<F: Fn(&Self) + 'static>(
&self,
f: F
) -> SignalHandlerId;
fn connect_visible_window_notify<F: Fn(&Self) + 'static>(
&self,
f: F
) -> SignalHandlerId;
}
Expand description
Required Methods
fn is_above_child(&self) -> bool
fn is_above_child(&self) -> bool
Returns whether the event box window is above or below the
windows of its child. See set_above_child()
for details.
Returns
true
if the event box window is above the
window of its child
fn is_visible_window(&self) -> bool
fn is_visible_window(&self) -> bool
Returns whether the event box has a visible window.
See set_visible_window()
for details.
Returns
true
if the event box window is visible
fn set_above_child(&self, above_child: bool)
fn set_above_child(&self, above_child: bool)
Set whether the event box window is positioned above the windows of its child, as opposed to below it. If the window is above, all events inside the event box will go to the event box. If the window is below, events in windows of child widgets will first got to that widget, and then to its parents.
The default is to keep the window below the child.
above_child
true
if the event box window is above its child
fn set_visible_window(&self, visible_window: bool)
fn set_visible_window(&self, visible_window: bool)
Set whether the event box uses a visible or invisible child window. The default is to use visible windows.
In an invisible window event box, the window that the
event box creates is a GDK_INPUT_ONLY
window, which
means that it is invisible and only serves to receive
events.
A visible window event box creates a visible (GDK_INPUT_OUTPUT
)
window that acts as the parent window for all the widgets
contained in the event box.
You should generally make your event box invisible if you just want to trap events. Creating a visible window may cause artifacts that are visible to the user, especially if the user is using a theme with gradients or pixmaps.
The main reason to create a non input-only event box is if you want to set the background to a different color or draw on it.
There is one unexpected issue for an invisible event box that has its
window below the child. (See set_above_child()
.)
Since the input-only window is not an ancestor window of any windows
that descendent widgets of the event box create, events on these
windows aren’t propagated up by the windowing system, but only by GTK+.
The practical effect of this is if an event isn’t in the event
mask for the descendant window (see WidgetExtManual::add_events()
),
it won’t be received by the event box.
This problem doesn’t occur for visible event boxes, because in that case, the event box window is actually the ancestor of the descendant windows, not just at the same place on the screen.
visible_window
true
to make the event box have a visible window