Haxe

or does it get called even on the close button in the corner?

button being the `DialogButton`that was clicked, so "OK", "Close", etc

yeah, that counts as `DialogButton.CLOSE` i believe

fyi, you dont have to go down the validateDialog route if you dont wont (for, lets say stopping the dialog from closing on bad input)

you can also listen for `DialogEvent.DIALOG_CLOSED` and cancel that event

however, the validateDialog is good for if its async... like lets say a login dialog

also, fyi 🙂

```haxe
        dialogCloseButton.onClick = function(e) {
            hideDialog(DialogButton.CANCEL);
        }
```

so the X in the dialog title is `DialogButton.CANCEL` not `DialogButton.CLOSE`

so a button added with `DialogButton.CANCEL` will return that for both the X  in the corner and the cancel button added to the dialogue?

yeah, feels a little wrong to me to be honest, i feel like it should be CLOSE, not CANCEL

yeah, semantics i suppose.... but i can see a dialog with "cancel" button and a "close" button... and cancel meaning something like "cancel this action" not "cancel this dialog"

then again, i can see it the other way round also

as long as someone isn't trying to develop their entire workflow in one dialogue, it doesn't make a huge difference imo

yeah, i suppose, it hasnt come up before, so ill assume no one cares that much 😄

<@!385014891750096896> I created an issue in relation to Float32Array and similar being reimplemented for all toolkits, it's really not ideal for libraries like HaxeUI, and seems that the current implementations need improvements.  I am not sure if it will get closed... but if you think it's relevant please do pitch in.

I know for any shader stuff for instance consistant Float32Array would be useful, and UInt8Array for perhaps pixel manipulation.

unsure on sound but guessing one of these arrays is used.

Not seen toolkits using the standard ones and for c++ and js you normally have to have different stuff, for the amount of real use they need to be reconsidered.

https://github.com/HaxeFoundation/haxe/issues/10549

... im digging the new number steppers... ill support the old ("classic") layout also, since the poll was basically down the middle :/

I always found the side buttons for steppers were much easier if the user was using touch, even occasionally

in an older web project I ended up making them out of regular stepper fields with the controls hidden, with two buttons (or styled links) to emulate the side buttons