wxUpdateUIEvent(3)

📦
version 29.0.6 · 3 versions
, in ubuntu stonking

💖 wxUpdateUIEvent 💖

okay bestie, welcome to the wxUpdateUIEvent page — it's a module from the Erlang wx bindings, and it's genuinely one of the good ones. no cap. 💅

✨ NAME ✨

wxUpdateUIEvent — this class is used for pseudo-events which are called by wxWidgets to give an application the chance to update various user interface elements.

so basically it's the little helper that keeps your menus and toolbars looking correct without you having to micromanage them. iconic behavior fr fr. 👑

🌸 DESCRIPTION 🌸

okay so imagine life WITHOUT update UI events. an application has to work hard to check/uncheck, enable/disable, show/hide, and set the text for elements such as menu items and toolbar buttons. and the code for doing all that? it has to be mixed up with the code that is invoked when an action is invoked for a menu item or button. it's giving spaghetti. 😭 not the vibe.

WITH update UI events tho, you define an event handler to look at the state of the application and change UI elements accordingly. wxWidgets will call your member functions in idle time, so you don't have to worry where to call this code. it just… happens. main character energy honestly ✨

and it's not just cleaner — it's also a clearer and more declarative method, and it means you don't have to worry whether you're updating a toolbar or menubar identifier. the same handler can update a menu item and a toolbar button, if the identifier is the same. instead of directly manipulating the menu or button, you call functions in the event object, such as check/2. wxWidgets will determine whether such a call has been made, and which UI element to update. she does the detective work for you 🕵️♀️💖

these events will work for popup menus as well as menubars. just before a menu is popped up, wxMenu::UpdateUI (not implemented in wx) is called to process any UI events for the window that owns the menu.

now — if you find that the overhead of UI update processing is affecting your application, you can do one or both of the following:

  • Call setMode/1 with a value of wxUPDATE_UI_PROCESS_SPECIFIED, and set the extra style wxWS_EX_PROCESS_UI_UPDATES for every window that should receive update events. no other windows will receive update events. strict guest list bestie 🎀
  • Call setUpdateInterval/1 with a millisecond value to set the delay between updates. you may need to call wxWindow:updateWindowUI/2 at critical points, for example when a dialog is about to be shown, in case the user sees a slight delay before windows are updated.
ngl there's a lil gotcha here: note that although events are sent in idle time, defining a wxIdleEvent handler for a window does not affect this because the events are sent from wxWindow::OnInternalIdle (not implemented in wx) which is always called in idle time. 🫶

wxWidgets tries to optimize update events on some platforms. on Windows and GTK+, events for menubar items are only sent when the menu is about to be shown, and not in idle time. efficiency slay 💅

See: Overview events

this class is derived, and can use functions, from:

  • wxCommandEvent
  • wxEvent

wxWidgets docs: wxUpdateUIEvent

🌈 Events 🌈

use wxEvtHandler:connect/3 with wxUpdateUIEventType to subscribe to events of this type. that's the whole vibe check right there ⭐

🦋 DATA TYPES 🦋

  • wxUpdateUI() :: #wxUpdateUI{}.
  • wxUpdateUIEvent() :: wx:wx_object().
  • wxUpdateUIEventType() :: update_ui.

💜 FUNCTIONS 💜

  • canUpdate(Window) -> boolean() when Window :: wxWindow:wxWindow().

returns true if it is appropriate to update (send UI update events to) this window. literally a "should i text them" function, and the answer is usually yes 🥰

this function looks at the mode used (see setMode/1), the wxWS_EX_PROCESS_UI_UPDATES flag in window, the time update events were last sent in idle time, and the update interval, to determine whether events should be sent to this window now. by default this will always return true because the update mode is initially wxUPDATE_UI_PROCESS_ALL and the interval is set to 0; so update events will be sent as often as possible. you can reduce the frequency that events are sent by changing the mode and/or setting an update interval. pace yourself queen 👑

See:

  • resetUpdateTime/0
  • setUpdateInterval/1
  • setMode/1
  • check(This, Check) -> ok when This :: wxUpdateUIEvent(), Check :: boolean().

check or uncheck the UI element. box ticked, dopamine delivered ✅✨

  • enable(This, Enable) -> ok when This :: wxUpdateUIEvent(), Enable :: boolean().

enable or disable the UI element. grayed out or fully alive, your call 💅

  • getChecked(This) -> boolean() when This :: wxUpdateUIEvent().

returns true if the UI element should be checked.

  • getEnabled(This) -> boolean() when This :: wxUpdateUIEvent().

returns true if the UI element should be enabled.

  • getMode() -> wx:wx_enum().

static function returning a value specifying how wxWidgets will send update events: to all windows, or only to those which specify that they will process the events. it's the "everyone invited" vs "private party" switch 🎀

See: setMode/1

  • getSetChecked(This) -> boolean() when This :: wxUpdateUIEvent().

returns true if the application has called check/2.

for wxWidgets internal use only. dw about it bestie, not your business 🙈

  • getSetEnabled(This) -> boolean() when This :: wxUpdateUIEvent().

returns true if the application has called enable/2.

for wxWidgets internal use only.

  • getSetShown(This) -> boolean() when This :: wxUpdateUIEvent().

returns true if the application has called show/2.

for wxWidgets internal use only.

  • getSetText(This) -> boolean() when This :: wxUpdateUIEvent().

returns true if the application has called setText/2.

for wxWidgets internal use only.

  • getShown(This) -> boolean() when This :: wxUpdateUIEvent().

returns true if the UI element should be shown. visible and thriving 🌟

  • getText(This) -> unicode:charlist() when This :: wxUpdateUIEvent().

returns the text that should be set for the UI element.

  • getUpdateInterval() -> integer().

returns the current interval between updates in milliseconds.

the value -1 disables updates, 0 updates as frequently as possible. zero chill, literally 🏃♀️

See: setUpdateInterval/1

  • resetUpdateTime() -> ok.

used internally to reset the last-updated time to the current time. it's the "mark as read" of UI updates 🫶

it is assumed that update events are normally sent in idle time, so this is called at the end of idle processing.

See:

  • canUpdate/1
  • setUpdateInterval/1
  • setMode/1
  • setMode(Mode) -> ok when Mode :: wx:wx_enum().

specify how wxWidgets will send update events: to all windows, or only to those which specify that they will process the events. you're literally setting the guest list policy ✨

  • setText(This, Text) -> ok when This :: wxUpdateUIEvent(), Text :: unicode:chardata().

sets the text for this UI element. words! give it words 📝💖

  • setUpdateInterval(UpdateInterval) -> ok when UpdateInterval :: integer().

sets the interval between updates in milliseconds.

set to -1 to disable updates, or to 0 to update as frequently as possible. the default is 0.

use this to reduce the overhead of UI update events if your application has a lot of windows. if you set the value to -1 or greater than 0, you may also need to call wxWindow:updateWindowUI/2 at appropriate points in your application, such as when a dialog is about to be shown.

  • show(This, Show) -> ok when This :: wxUpdateUIEvent(), Show :: boolean().

show or hide the UI element. peekaboo 🫣✨

and that's the whole page bestie, you ate it fr fr 🌈💖 thanks for reading, go update some UI elements and be iconic about it. 👑

byeee, brought to you by Ericsson AB, wx 2.6, wxUpdateUIEvent(3) — mwah 💋🎀

📦 where this page comes from