Xojo 2019R2 has a lot of new features and enhancements, including the simplification of updating the User Interface in apps from threads running in combination with the main app thread. Doing that in previous releases required the use of a thread in combination with a Timer, for example.
It was reported that Apple is rejecting from the Mac App Store apps written using the Electron framework. This is where we see the advantage of writing a native application.
You might be assuming you absolutely must upgrade to API 2.0 right now, but that’s not the case. We have designed it so that you have tremendous flexibility in terms of what and when and even if you move to API 2.0.
2019r2 has many changes related to API 2.0. Most of your projects should open and run without any changes. You can then switch code to API 2.0 when you want (or not at all — it’s up to you).
As an Object Oriented Programming language (OOP), Xojo’s data types, especially the non-primitive ones, use or can use a Class hierarchy. This means that one class, either included by default in the Xojo Framework or created from scratch, can act as a base or root class for other classes based upon them.
Apple just released Apple Transporter to manually upload apps to the Mac and iOS App Stores.
The Xojo Doc site has several thousand pages of information. To make it easier to quickly find things in the online docs, topics are categorized. You can find categories that a topic belongs to at the bottom of its page.
Among the many IDE improvements in 2019r2 we’ve made some improvements in how the Control Layout Locks work so even if a control is locked, it’ll still obey the left/top/right/bottom alignment locks. We are taking some hints from the way many graphic design programs approach this and we think it’ll be a big improvement to the way controls are organized on Windows and Containers.
At XDC 2019, I did a session called Avoiding Troubleshooting Troubles, which was essentially about ways to take advantage of the Xojo debugger. During the…
If you’re starting to program with Xojo, then you’ll probably soon find yourself in a situation where you need to use one of the Container types: Array. In this case, it’s also probable that you might be confused at first as to why you don’t get what you expected when assigning the contents of a source Array to a target Array via the assignment operator (“=”).