This bug is scheduled for r3. But as your project get larger it slows down even more (kind of like the mythical load stone. The faster you run the heaver it gets) Literarily a ten minute load time on a very new M1 mac.
Text format seems to load the slowest. Also windows and containers with lots of controls load really slowly. I now have over 650 project items and loading the project isn’t really bad in xml.
Unfortunately we’re having to use text because we use it GIT.
The one thing I really noticed is that it loads the first third of the project in under 30 seconds the second third of the project takes three minutes and the last third of the project takes even longer. It seems to slow down as it loads more and mo
Our biggest project contains 243 Windows, 250 Modules and 805 classes. The time to load this project in xojo text Format is about 50 seconds on a core i9 MacBook Pro. So we have nothing to complain.
Both project types, Desktop and Web, will open much faster in 2022r3. It won’t be possible to ship this improvement earlier, as it needs to be tested thoroughly. The changes weren’t trivial.
Do you embed images, icons inside the Xojo Project ?
If so, and you are using macOS, you have to know that one icns (or png) icon is heavy, insanely large (1024 x 1024)/
Also, loading / saving process image and this takes time.
Loading them dynamically resize down the project file and speed-up the open / save times.
Another slow down is the hard disk (even SSD) lack of free space. Under 50 GB of Free Space you must await a slow down.
Regular shut down and reboot also allows to speed things up (even if some people told you the reverse: let them do what they love and test by yourself).
BTW: you do not disclosed the used OS, nor the Xojo Project Size.
Drawing the TABs…
I had a slow SSD based Windows machine, long time ago, at at boot time, I was able to watch the tab drawing one after another… but the laptop was a slow one (and I do not cared because I Power On the laptop and do something else until the process was done !).
@Jay_Menna Unfortunately, I have been struggling with it for more than a year so I understand your frustration. I had created a forum post on the test channel, a feedback case, mentioned the problem privately to greg complete with video, reported to Geoff privately along with a list of bugs but nothing. If you didn’t raise the case I don’t think it would have been fixed for 2022r3 either. So for me it is already a step forward! Thank you