I’m curious how many of the new issues are Android only. As a new target I would expect a lot of issues reported against it.
In my ideal world I want to know how many new and closed issues were for each target type (desktop, web, mobile) or even by OS (Mac, Win, Linux, iOS, Android, RPi) and how many reported against the IDE. But then there are so many variations on targets these days it wouldn’t tell you much. I could be wrong.
macOS: Preferences… menu item is named now Settings… when the IDE is ran on macOS Ventura. (72342)
Erm… This one is auto-handled by the macOS, unless they’re doing something really wrong.
Desktop: DesktopMoviePlayer: renamed MovieStarted to PlaybackStarted and MovieStopped to PlaybackStopped for consistency with the MobileMoviePlayer. (69018)
Superb, because that’s what we wanted, more changes to the fucking names.
macOS: App no longer crashes when accessing the RuntimeException.Stack in certain situations, especially when sandboxed on Intel macOS Ventura. (72314)
Now that’s more like it.
macOS: macOS builds no longer include an invalid rpath, which some apps have flagged as being incorrect by using an additional path separator. (64896)
Wait… Could it be, this is one of my feedbacks that has actually gotten addressed. Fucking A.
macOS: Fixed Color.FrameColor on macOS so it returns the expected color value. (69696)
One caveat though
The #'s I see will likely NOT be the same as what you see since it will depend on things like confidential cases I can see vs what you can see
And thats likely to differ
but those #'s will be in the right ballpark give or take a few
Yeah I had started a project in an earlier version of the Android beta
Reopened it and they renamed shit in there already
So I had to go "fix"code that wasn’t even a month old
But don’t worry, Geoff’s trying to train ChatGPT to write Xojo code and bake it into the IDE, so in the future, it will take even less time to re-write your existing apps into the current version of Xojo.
Sheesh… It’s like he heard what we’ve been complaining about and then decided to do more… Just fix the damn bugs, inefficiencies and work on things like Aliases, Macros, pre-emptive threading etc… You know, things that will actually lead to better quality apps.
Well, Android SUCKS. Compiler error with a simple msgbox it feels like some proof of concept or pre-apha release.
BUT that XAMLContainer is really interesting. For one thing, xojo FINALLY have a way to use the native renderer (WebView2) after ditching it in the WebView control.
This can really improve the windows target.
It is a shame that there is no XAML window and visual designer for it, with all the controls created in the same container. For now, having each control in their own canvas container can have a performance hit, but it looks promissing.
Nothing against Björn and Christian, I used their Addons a lot (Björns’ more than Christians’) but compared with everything in the open source sphere or even enterprise commercial sphere Xojo was/is… how to put it in polite words… uhm… special kind of scam?
And using a Webview (the bloatware of a fully webbrowser) for your basic app UI is disgusting. Then better use https://sciter.com/ or https://flutter.dev/ - less pain with more features…
Have I mentioned… Sciter uses C-Interfaces… ideal for Freebasic…