I only wanted to let you know that. 
Hi Julia,
sorry for my lack of clarity about the subject!, my lack of interest in 19r3.1 or whatever, and to be honest why I would not use it, is not the slowness as was suggested.
I can not comment on that, I don’t use it.
my flag is firmly flying in 19r1.1 as it is COMPLETELY API2 agnostic, it does not have any of the stupid event name changes and to all intents and purposes it it the last ever version of web1(not that that makes it great, its just a fact) and the last viable production compiler Xojo will have available for maybe a year, more? I don’t know.
post 19r1.1 seems to be when Xojo towers had an embolism, things were just starting to gain a traction, bugs were getting fixed, then BOOM, some idiot decided to change all the event names and drop API2 at the same time, really? why screw a huge number of serious customer all at the same time, some one in charge needs to take a holiday, for a long time and let serious people look after the tools.
hence my comment ‘until 19r1 stops working’, I honestly don’t think we are going to see a stable release for a very significant time, thank goodness thats just my opinion…
Thats what I really meant, sorry to be a bit vague.
Mark
1 Like
The event name changes in r2 were reversed in r2.1, and that remains the case for r3 and r3.1, and 2020r1 whenever we get it.
If you’re going to complain, complain correctly.
I might be wrong but I seem to recall someone said that they are coming back in disguise: as new controls.
Yes, supposedly there will be some new controls at some point which will have new event names. That will be a nuisance in that one has to remember what is equivalent to what. And I imagine it might be a problem to copy/paste, say, the Open event handler into a new control whose equivalent event is “Opening”.
I’ve not seen much information about this or much discussion about possible issues.
There is already a new SegmentedControl, called SegmentedButton in r3.x. I’ve not tried it incase I have to go back to a previous version of Xojo.
Geoff said this
Think he mentioned it in the 2020 XDC video as the interview with Paul
LOL
If you are going to critizice, at least read carefully, he is complaining about the API2 (“flying in 19r1.1 as it is COMPLETELY API2 agnostic”). The event names were just mentioned as being part of the 2019r2 release, and that is just a fact.
And Markus is right, Xojo said in the forums that Web2 Will have API2 Event names, and that they are going to replace ALL the controls in the other platforms with ones having the API 2 event names.
I cant say I heard them say “replace all existing controls” but that they would have new controls with all the new event names
So we’ll have 2 versions of label, cancel button etc etc etc
An “old one” with the old event names and a “new one” with the new event name
Its at about 20:30 in this video
Replace them via deprecation. Look at the SegmentedControl, In new proyects with API2 IDEs, you cant add from the library, you cant chang other control to that class, so, you can only use the replacement SegmentedButton even if SegmentedControl is still there. If you open an old proyect, the IDE will load the SegmentedControl can use them.
That is only one example
I dont believe they are going to do that with every control
They basically marked SegmentedControl “deprecated” and are probably using that attribute to determine whether they should allow you to set a new instance to that super
Haven’t tried this BUT if you start a project and save it in 2019r1.1 then open that in 2019r3.1 can you add a new segmented control ?
Yes, even if the proyect does not use segmented control itself. Only new proyects are restricted. Also works if you have an old IDE and copy a segmented control from there.
Well, you know what happens when someone at xojo says “this must happen”. Reversing the new names was only because they couldnt solve compatibility issues. But…
Having current classes just for compatibility and forcing you to use the new ones on new proyects or the aparent focus, force them on new users like the older ones never existed, is something you cant believe?
Then we know what the answer is
Create a new default project and make it so the IDE never uses the built in Desktop Template and start from one that is created in 2019r1.1 and then things return to normal 
Here’s the “how to”
http://docs.xojo.com/UserGuide:Project_Types#Changing_Default_Projects
Yeah one of the few things that does NOT have compatibility flags is events
So its not possible to tag one event as being “Desktop” only like you can with so many other things
Making THAT possible seems to me it would have permitted them to make these chnages and NOT break everything in the process
But … 
Yes
The belief seems to be that MOST users, upon getting a new version, immediately update EVERY project they have to the latest version.
I’m sure some do.
But there are a non-zero number that do NOT do that because they do use older versions to continue to support system that have been dropped by more recent versions of Xojo.
You can never really successfully deprecate very much. Look at HTML. We had the XHTML people who were pushing the idea that only completely correct web pages would render AT ALL. “Wrong” pages would display an error rmessage saying “the page you are trying to display has incorrect markup”. And they would deprecate stuff like <center></center> and if you used them - no rendering just the error message. Fortunately the more sensible HTML5 people came along and realised that in the real world, there are and will remain millions of websites with wrong HTML. So instead of erroring them they worked out how to handle wrong HTML.
And so today if you use <center></center> it will render correctly just as it did 20 years ago. Such “deprecated” stuff will never have support for it removed from web browsers - no browser would dare risk being unable to render some important website.
So I can’t see Xojo actually removing anything.
Not sure why he’s compaining about API2 and therefore thinking he has to stay with 19r1.1. It’s 19r2.1 and later that are the ones that are agnostic - they dont care if you use API1 or API2. OTOH, 19r1.1 is ignorant of API2 - it won’t let you use it.
AFAIK, you can use API1 in 19r3.1 with no changes at all.
1 Like
Because experience teaches us that no effort at all will be put into API 1 so what is the point of using a higher version?
True, but new features will be added - new methods, new classes. I was able to throw out a couple of classes by using new features - such as a subclass of Date I made, to which I’d added SecondsSince1970.
My ‘complaints’ Clothears, or concern as I call them, with respect to API2, and more especially the new event names, is that it APPEARS to be a poorly thought out process, dumped on the users base following a significant negative reaction during pre release testing, by all the people who are heavy duty users and use the tool to support their families and people who work for them.
the result was a number of extremely well known users dumping the tool and moving on as it was the last straw for a lot of people in a very long line of less drastic but equally odd decisions.
API2 has now introduced a number of new bugs in the new controls, serial for instance, why on earth change a perfectly working class for a poorly tested new version.
I cannot attest to other issues as I am just not willing to waste my time figuring out a new set of controls and a new set of bugs, its supposed to be a RAD environment, rapid application design, nope thats gone a long time ago.
I repeat a previous comment, 19r1 has a lot of bugs, but they are almost all known, there are work arounds and largely this means its a usable product.
anything with API2 will introduce a whole load of new bugs, that will also never likely get fixed, but as it stands no one knows about enough of them.
you suggest nothing depreciated is ever really lost, I wonder if you missed the notes above.
Web 1.0 is gone, there will be no Web 1.0 in 21r1, sorry 20r1, thats not depreciation it is destruction.
if you have any version prior to the unreleased versions of the IDE (and I say this with the caveat that we are in a pre release phase of BS and something might change) then the IDE does not run in Rosetta2, it has apparently been fixed in an upcoming 2020 release, suggesting to me, and I am perfectly happy to be corrected, that the issue is in the Xojo IDE, now depreciated, and the current version, and ALL previous versions of RB/Xojo ever made will be unusable in the new MciOS.
again that is a bit more than depreciated.
my argument is that the post 19r1 versions of the compiler are almost like going back to RB V1.
absolutely everything existing is going to be replaced (at some point going forward), and everything is going to have a bug in it, throw in the mix ARM, now honestly consider just how many years is it going to take the product to become as reliable and bug free as the most mature version we have which has just been totally abandoned.
my own opinion is there will be a 2 to 5 year period before the system is close to being as stable as the one currently available, well I say stable, there will be some parts no doubt that will be better than others for sure.
but web2, totally new, android, jeees, totally new despite being promised for I can’t remember how many years, no one has ever even seen a beta of it, iOS, needs a total rewrite, so its going to be new also, MaciOS versions, thats obviously going to be a breeze, yup, and a whole heap of other stuff we have all forgotten about, PDF, workers, remember them?
19r1 is the most able, most supported and stable low bug version of the product there has ever been since day 1.
its just been put in the bin and a new one started, it might be that there are a number of people who are just as disappointed that their long term work and commitment to the product has seemingly been flushed down the toilet to give a new area of focus.
which brings me to the OP, I asked at the start ‘Where is Xojo Focus?’, I still have no friggin idea, it does not appear to be anyone I know or anyone on the Xojo forum, perhaps the focus is in Geoffs mind and thats all it needs to be, hang every one else.
keep the faith Clothears, if it works for you then that is great, lets hope you come back in a couple of years and tell us how its going.
1 Like
Web 1.0 will not exist in 2020r1 or any newer versions
Gone
Its a one way trip to the newer version
You must have a special version of 2019r1 as the one we are using isn’t the most stable low bug version of the product there has ever been since day 1.
1 Like