The number of bug fixes in any release is irrelevant. Check out Feedback how many new bugs they get each day.
2021r2? That only had 4 more bug fixes than the 2021r1 “non-bug fix” release just before it so I’m not sure how that really classifies as a “bug fix” release.
Not really though, if they have properties/events etc that exist on one platform and not another then there can be collisions with implementation and documentation. Separating them out this way ensures that this doesn’t happen. It can probably (I’ve not double checked this) then be down to the user to implement their own subclasses to work around this and create a common set of exposed properties/events etc. that they can then use across multiple platforms if they wish. I’d rather have more functionality across multiple types of buttons than narrowing everything down to a common pool that isn’t as feature rich.
Totally incorrect… a “button” could have properties on one platform and not another, and the compiler would still be able to deal with it. Particularly since referencing a property in your code that was inappropiate for the platform the code was destined for would be an error anyways.
And no where did I imply, this would require coding to the lowest common denomitor, because it wouldn’t, Each platform could be a feature rich (and different) as required.
So if properly designed, this approach works just fine. As a matter of fact I have designed a framework for use with Swift… it defines a dsBUTTON… That control works seamlessly on iOS/macOS and even on AppleTV deployments. So if “I” can do it, so could they.
Not to mention they just killed the “code once, deploy many” mantra.
So, lets just agree to disagree… In my opinion, Xojo screwed the pooch once again
Exactly. When you have to beg the CEO to get a bug fixed, there’s a problem. And then it’s all excuses.
Xojo isn’t really cross platform and really not all native. Somewhat cross platform and somewhat native would be true.
Yeah because it would be so nice to open the Button docs in desktop and wade through all the properties, methods and events for it that just say “Web only”/“Mobile only” or if they hid them away then when you browsed the docs or used autocomplete then you’d be scratching your head when you moved your project from desktop to web and you accidentally implemented something that existed on Web but you weren’t told about it under Desktop. It doesn’t make it fluffy and easy to use for their target audience.
As for “code once, deploy many” I’m not sure they’ve been able to claim that for a long time considering the number of fudges and workarounds that need to be done across all the platforms if you get past a window with a textfield and a button on it. It might be the case for “someone” who just tinkers on a single platform in some kind of utopian bubble but for anyone slightly more adventurous with an eye for things that are slightly out of place from os standard then its certainly not a case of copy the project over and hit run.
Well, I tried converting a small app from 2021r2 to 2021r3 to check out the process and the API 2.0. All I can say at this point is that it is a good thing the old code will continue to work.
Is it easy to update a control? Yes, mostly. You will have to go and change the references to the controls enumeration values (Listbox.ColumnAlignments… becomes DesktopListbox.ColumnAlignments…, etc.) The same goes for ComboBoxes and PopupMenus.
One real kicker is that if you “update” the MenuBar to DesktopMenuBar, besides all references you will have to update all windows in the app. That includes document windows, the About Box if your app has one, and any custom windows. Which means that if you update the MenuBar to API 2.0, pretty much results in having to update the entire app.
As a hobbyist, I’m unlikely to move to 2021r3 unless I get really bored and have nothing else to do.
There is no code once deploy many like the java wora concept
How does renaming controls HELP users ?
Fix the open reproducible bugs ?
I have nearly 200
Julian has another huge pile
THAT would help users and probably even win kudos
I’m not sure thats the right word but … we’ll see wont we ?
Naw we’re just really skeptical about the changes geoff
EDIT : or person that sure sounds like geoff
Didn’t Geoff insist on people using their real name? Surely he would not use a pseudonym to hide behind!? That would be a case of “Do as I say, not as I do”, wouldn’t it?
Surely not.
What would be the problem with using your own name anyway? I do it all the time …
There is most definitely a way to do something better than separate top level classes for each platform
Now you cannot write any common code that might deal with a Control since WebButton, DesktopButton iOS button and MobileButton dont even have a common super class of UI Control or Control
Right at this moment I’m literally having to rewrite code from desktop to Web because of exactly this
(Never mind that how control embedding etc on web works is totally different than desktop)
Yeah I could pass in a variant, as was once suggested by the CEO, but this is a step backwards
Now what used to be a compile error caught early is a runtime error
A lack of imagination about HOW to do this is whats truly disappointing
Instead we have this 
Well, that souns just like Xojo marketing. Hey, we had no mayor aditions this time, lets call it “bug fix release” 
They need to fix at least twice the normal bugs to be called BIG “bug fix release”
I’m not Geoff, but he’s not wrong. Some folks here have obviously moved on and it looks doubtful there’s anything that could be done to bring them back.
For the record, I’m still a fence sitter.
True BUT, there is a LOT that he could do to prevent more and more people leaving…
… but with the latest release I got pushed even further off the fence … it is not so much only WHAT they are doing, but the HOW too. It just seems so … cobbled together. Clunky. Inelegant. That MapLocation is still so horrendously handicapped is unforgivable.
I absolutely LOVED REALbasic. But Xojo is lacking the simplicity and elegance that REALbasic had. It is fugly. And not because it couldn’t be made to shine.
And then there is what isn’t being said. Again. Yes, you can still use the old desktop controls … just don’t expect any bug fixes. That isn’t support, that is “on life-support” …
Xojo just gives me more and more bad vibes. Starting up Xojo evokes dread for me. Dread that not even Windows managed …
Join the club
I still have clients using it with varying degrees of success - esp web 2
If I would have to take care of clients with it I would want to run away.