#Xojo 2020 for mac#
#Xojo 2020 install#
#Xojo 2020 driver#

And some of the effects can also do it in asynchronous mode. The PictureEffectsRaw plugin for Xojo enables you to do advanced image processing in Xojo using up to 8 CPU cores at once. Sigh.PictureEffectsRaw 4.5 is out and TypeLib 9.3.4

#Xojo 2020 driver#

Since this is the main project I work on, that means I likely won’t be updating my daily driver mac from Catalina for some time. So I either bite the bullet and spend however long it takes to refactor my UI to work with more recent Xojo versions, or I keep a Catalina mac around just for this project. In the mean time, I have to keep the Xojo version maintained. We’ve already begun a complete ground-up re-write using a completely different platform, but that won’t be ready for more than a year. To fix it, I’m looking at a pretty major re-write, and this is a massive project with a codebase nearly 15 years in the making.

#Xojo 2020 for mac#

This project currently compiles correctly for Windows only in Xojo 2017R3, and for Mac only in Xojo 2019R1.1. For now, I’m simply going to have to keep a Catalina mac available to compile this specific project until it can be fixed to build in the most recent versions of Xojo.įor anyone curious: my issues are not related to API2 (yet), but rather with UI/drawing issues both on Windows and on OS X. Once Rosetta was installed, Xojo 2019R1.1 will launch, but it will not compile anything, and I don’t expect Xojo to bring any official support to older versions - which puts me in a tough position.

The mac was probably still doing a bunch of first run junk in the background, and I simply beat it to the punch. It is a bit odd that it took several minutes for these prompts to appear, but it’s likely due to literally taking the computer out of the box, setting up a user account, downloading Xojo and trying it.

#Xojo 2020 install#

Some time later (after writing the original post in this thread) I came back to that mac and had some messages about needing to install Rosetta so that Xojo would run. The first 3 times I tried to launch Xojo it just completely failed to run, and in checking the console I saw error messages there which lead me to believe what I quoted above. I’m guessing that when 2019 was written there was no expectation that OS X 11 would ever get released… so the logic just looks at the minor version, which fails in Big Sur because it is 11.0.Ī little update: Trying Xojo was literally the first thing I did as soon as I got the new user account created etc on the new M1 MacBook Air.

In looking at the system logs, it appears that Xojo checks for a system version of 10.10 or newer, and fails so it quits. If it was a deprecation and they fixed it earlier, more Xojo versions would be working on Big Sur. This is why I always urge people to fix their deprecations sooner rather than later. Probably using something that was deprecated and Apple finally removed. I’m not 100% sure why, but they produce an compile error, in UIFramework if I recall correctly. 19r3.1 and earlier just won’t work on Big Sur. How far back would they need to go? Won’t there always be somebody unsatisfied? It’s just an unfortunate fact of life. It was something like a week after the first beta shipped, if I remember correctly.īut you can’t expect them to issue new versions of every older version. Wow, look at this list of things that won’t happen.