![]() There appears to be no way to make `on-demand' work right for the Unity window manager's global menu bar, since there's no notificiation when the menu bar is clicked. We approximate the correct behavior by calling `on-demand' when a containing frame loses the keyboard focus, which might be because the menu bar was clicked; that may be too late (because the menu has already been shown), but it should work most of the time. Closes PR 13347. Relevant to PR 13395, but DrRacket will have to change to work around the remaining limitations of `on-demand'. |
||
---|---|---|
.. | ||
button.rkt | ||
canvas.rkt | ||
check-box.rkt | ||
choice.rkt | ||
client-window.rkt | ||
clipboard.rkt | ||
colordialog.rkt | ||
combo.rkt | ||
const.rkt | ||
cursor.rkt | ||
dc.rkt | ||
dialog.rkt | ||
filedialog.rkt | ||
frame.rkt | ||
gauge.rkt | ||
gcwin.rkt | ||
gl-context.rkt | ||
group-panel.rkt | ||
init.rkt | ||
item.rkt | ||
keycode.rkt | ||
keymap.rkt | ||
list-box.rkt | ||
menu-bar.rkt | ||
menu-item.rkt | ||
menu.rkt | ||
message.rkt | ||
panel.rkt | ||
pixbuf.rkt | ||
platform.rkt | ||
printer-dc.rkt | ||
procs.rkt | ||
queue.rkt | ||
radio-box.rkt | ||
README.txt | ||
slider.rkt | ||
stddialog.rkt | ||
style.rkt | ||
tab-panel.rkt | ||
types.rkt | ||
unique.rkt | ||
utils.rkt | ||
w32.rkt | ||
widget.rkt | ||
win32.rkt | ||
window.rkt | ||
x11.rkt |
Allocation rules: * Use `as-gtk-allocation' when creating a Gtk widget that is the main container for a given window<%> object. When the resulting reference becomes unreachable, the widget will be released with gtk_widget_destroy() through a finalizer. * Use `atomically' to create and attach a sub-widget within the main widget. Don't use gtk_widget_destroy(); the containing widget will destroy the enclosing widget. * For temporary objects, use `atomically' to wrap both the allocation and release. Every call to a function whose name contains "new" needs to be in one of those cases.