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.
Me too. But I already went through this in the iOS > Mobile transition. It took hours to update one of my apps to remove the deprecations. If I ever go back and update one of my old apps I will probably do the same thing again.
Yes, I know. But until/unless I find something that 2021r3 gives me that I need and don’t have in r2 I see no reason to expend the time and energy converting. As for any new project I start, well, I’ll decide then.
Note to past self, don’t be a muppet and take the time to RTFM.
I also found what was causing the error above, I hadn’t changed all the other components in the project, after doing that and turning back on “Menu Bar Visible” from the Gear in Window1 it loaded up quite nicely in 2021r2.1. Nice! Cheers all that pointed me in the right direction.