Possibly it is one of the hidden prices paying for Xplat with it. I can only say: I don’t have that problem with Java, not with Swing, not with JavaFX. So I guess it is an internal invention since it is also no problem with QT as I checked out also. Xojo has several problems located on all places of the IDE and the Compiler, this is only a small one.
Datatime makes problems, math makes Problems, the Database Connectors delivered with Xojo are a mess (bleeding slow and not stable), the Web->let’s not speak about, the Desktop is not really stable, not reliable and is suffering from Changes in it’s framework since the last versions of the last 12 months where it was already with API 2 in Production, IOS is let me say half ready and Android: may come soon or wait for reincarnation of Hare Krishna, who knows?
The amount of Bugs is still not less than before, 6670 open Issues at the moment like you can see at this pic here:
Screenshot made today, 11pm German time.
So, if I am looking on it, nothing really changed. That is a problem while many of the Bugs are Showstoppers and we are far away from the last Bug Bash.
The Docs are in chaos and the Software by self is driven by Libs which are older than my Grandkids. The UI is native but not really and the XPLat Idea behind is brilliant but they do not follow a clear XPLat Concept.
So what are we awaiting from Xojo? Is it the reducement of Bugs to0? No,that will never be happening before that the Hell is frozen, Flight to Mars costs only an hour and most of us are not on this planet while after own funeral.
Looking on the Feedbacks for Android it is still in an early pre Alpha Phase with many Compiler Errors which are a real problem to fix at the moment.
And yes, looking on it shocks me while I thought that there are less Bugs in Feedback. I realized today that the amount I that big.