VZ

12 ms·

1.
by VZ 5mo ago
wxRuby has been resurrected as wxRuby3, see https://mcorino.github.io/wxRuby3/ Among actively developed bindings, there is also wxRust at https://crates.io/crates/wxdragon
2.
by VZ 8mo ago
> wxWidgets is oldschool It's a bit sad that a GUI library absolutely needs to be new and shining to be even considered nowadays, it looks like the whole programming world got infected by JS ecosystem anything-that-is-more-than-3-mo
3.
by VZ 3y ago
You definitely should have been able to link statically, but my point was that these DLLs are already available on the wxWidgets site, you didn't need to upload them yourself...
4.
by VZ 3y ago
Interesting that you've decided to provide your own wxWidgets DLLs instead of using the official ones (see https://www.wxwidgets.org/downloads/ ). Is there some reason for this or did you just not know about the ex
5.
by VZ 3y ago
Well, there is only so much latitude for naming the event (or message, callback, whatever) sent when a window needs to repaint itself. Qt has `paintEvent()` too and nobody calls it MFC-like AFAIK. IME people mostly think about event table m
6.
by VZ 3y ago
This was indeed the case. In 1995. Since then just about everything has changed, but the idea that wxWidgets is MFC-like still refuses to die... Another common related opinion is that you have to use macros when using wxWidgets, which could
7.
by VZ 5y ago
This is very similar to my memories of Sven too, except that I didn't even manage to buy him a beer remotely. Good for you to have done it!
8.
by VZ 5y ago
> Still, they looked unusable. This shouldn't be the case. If you use wx 3.0, it's too old to support the features that appeared in macOS after its release (dark mode etc), but 3.1.5 should look just as the native UIs do.
9.
by VZ 5y ago
Best size is determined by each window. Min size is best size by default, but can be set to something different to override it. And the initial size is also min size by default, because this is what you'd expect: if you create a text e
10.
by VZ 5y ago
Be the change you want to be! wxC did exist but grew unmaintained, split into several variants (I think at least wxHaskell and wxErlang had their own versions) and withered. It shouldn't be that difficult to revive it but, well, somebo
11.
by VZ 5y ago
My answer at https://stackoverflow.com/a/19358996/15275 dates from 8 years ago but it's still relevant.
12.
by VZ 5y ago
FWIW updating from 3.1.4 to 3.1.5 (and then to 3.2.0) should be pretty seamless. The documentation does need work, but it's hard to find people volunteering to do it (although a few people do contribute to the docs too and this is some
13.
by VZ 5y ago
Maybe this has something to do with the fact that Windows doesn't have dark mode for the desktop applications in the first place.
14.
by VZ 5y ago
I can't say much for wxPython lib, but fixing high DPI support in native controls is the main focus of 3.2.0 and things look pretty good in 3.1.5 already IMHO. I could understand if you wrote that the layout system is not powerful enou
15.
by VZ 5y ago
It's neither a strength (there are definitely tons of things to do) but nor is it much of a weakness because the development is quite active pretty much all the time (just look at the commit history, PR merge rate or whatever). The mai
16.
by VZ 6y ago
I'd be interested to know what do you find rough about XRC (as wx XML layout system is known)?
17.
by VZ 6y ago
> Well, let's verify that… https://i.imgur.com/uHfjoUs.png No, they're not. Sorry, I don't know what is this supposed to prove, but I can definitely assure you that all the mentioned controls, and many oth
18.
by VZ 6y ago
ECMerge seems to use standard wxToolBar which is definitely a native control, so I don't know why it has the same background on all the screenshots. Perhaps they've explicitly changed it to make them more similar, I really can&#x2
19.
by VZ 6y ago
Sorry, but it was really surprising to see such an account of events. Just in case it's not obvious, and I realize that not everybody had a chance to be confronted by a giant corporation legal department in their lives, this was a rath
20.
by VZ 6y ago
I've completely forgotten about this page of the site, but it's nothing but polite fiction. We didn't really have any choice in the matter, it was that or be dragged in court by Microsoft lawyers and after spending some of my
21.
by VZ 6y ago
There are many screenshots here, I'm not sure which one do you mean. But do keep in mind that some of these screenshots (maybe even most of them) are 10, or 20, years old, so what seems non-native to you today might be just the way thi
22.
by VZ 6y ago
Wow, you have some interesting sources (care to share them?). Microsoft _forced_ us to change the name, threatening unspecified but dire legal consequences if we didn't. They have never sustained anything at all.
23.
by VZ 6y ago
> I submit that Wx implements its own non-native widgets. It does for the widgets that have no native equivalent, such as draggable/dockable tabs/panels that you show. You can't say they differ from native ones because the
24.
by VZ 6y ago
Both Codelite and Code::Blocks are written using wxWidgets.
25.
by VZ 6y ago
The really interesting thing would be to have a wx port using the native API for it, but unfortunately the last time I heard about wxBe was in the last century...
26.
by VZ 7y ago
wxWidgets provides "wxColor" typedef too however and many functions exist in both "colour" and "color" versions. There would be just too many bug reports about misspellings in the API otherwise.