wxNotifyEvent(3)

✨ NAME ✨

wxNotifyEvent — bestie, this one is the blueprint, not the main character. It's the base class for other event classes (like wxBookCtrlEvent), and it does not get used by the event handlers all by itself. It's giving "mom of the friend group" energy 💅

---

🦋 DESCRIPTION 🦋

Okay so when a control's state is actively being changed, it (or an object of a derived class, no cap) gets sent out — and it hands your program the power to veto/1 that change if it wants to stop it from happening at all. You have the authority. Use it wisely, queen 👑

See also: wxBookCtrlEvent

This class is derived from — and can use functions from — these iconic ancestors:

• wxCommandEvent
• wxEvent

wxWidgets docs: wxNotifyEvent

---

🌸 DATA TYPES 🌸

wxNotifyEvent() :: wx:wx_object().

---

💖 FUNCTIONS 💖

allow(This) -> ok when This :: wxNotifyEvent()

This is literally the opposite of veto/1 — it explicitly says okay, go ahead, the event may be processed.

fr fr, for most events you don't even need to call this, because they're allowed by default anyhow. But some events are forbidden by default (and the corresponding event description will tell you when that's the case, iykyk).

isAllowed(This) -> boolean() when This :: wxNotifyEvent()

Returns true if the change is allowed — meaning veto/1 has <em>not</em> been called — or false otherwise (i.e. it was called). Simple as that, no thoughts, head empty ✨

veto(This) -> ok when This :: wxNotifyEvent()

Prevents the change announced by this event from happening. Straight-up no. Shut it down. 🙈

Genuinely though, it's in general a good idea to tell the user why you're vetoing the change — because otherwise your application's behaviour (which just refuses to do what the user wants, out of nowhere 😭) might be quite surprising. Communicate, bestie. 🫶

---

Ericsson AB · wx 2.6 · wxNotifyEvent(3) — that's the whole page, babes! Go forth and veto responsibly, mwah 💋💖