Xeverous

I'm not able to test it on mac. I don't even have Obj-C skills. All from the sheet is from API documentation. I will left Mac implementation for you.

Implementation question: most (if not all) platforms require to hold or pass some platform-specific state to create any modal window. Should we make the modal functions members of the `window`...

I fkin love Microsoft... They provide a sample usage code on https://docs.microsoft.com/en-us/previous-versions/windows/desktop/legacy/bb776913(v=vs.85)?redirectedfrom=MSDN but it is not a complete function. Then this: > Note Several examples in this topic use the...

Funny thing: while reading the docs, I was concerned if they are up to date since 1 function was provided only 1 argument while it was declared to take 2....

Both WX and Qt implement these dialogs as a separate, standalone classes. In both librariers, constructors require a pointer to the parent window (possibly null pointer, but that is hardly...

> Elements require components that do not require a parent window. It's one of the fundamental requirements. The problem is, one can create multiple windows. And the modals on each...

I have a working Windows partial implementation. Interesting observation: there is no need to pass any state, but if I set the parent window to `nullptr` then the dialog is...

You might want to look: 02f50e1

> I respect your decision to use gcc, but keep in mind that this is not the mainstream compiler on Windows. Of course these changes are not intended for the...

@redtide elements has a very loose coupling of widgets and likely there won't be any models for trees. The best example is progress bar element: it doesn't expect any concrete...