As previously mentioned, I just bought a Windows Surface 11 Snapdragon (win 11 pro), a wonderful device in general, when you’re not looking for compatibility with all your usual tools.
Aside from the expected problems with OLE and ODBC and databases, I am having a lot of trouble opening Xojo projects created on other devices. I am not trying to run them, I’m trying to open them for editing. I’m not getting error numbers or messages. Xojo is just quitting 7/8 of the way through opening the document (Xojo launch speed is not great, compared to Intel or Mac Silicon m1, but not horrible once the project is open). This is true of imports from GitHub or from my network or from projects I copied over to my local drive.
If I’m referencing server databases, I would expect it not to run, but I would assume the project itself would be open to editing. And when I create new projects referencing ADO or ODBC, they open fine, they just don’t run (as expected).
Keep in mind that the SnapDragon processors are ARM-based processors and that the Xojo IDE on Windows is Intel x64. So the IDE is running emulated. Now, it’s entirely possible that parts of the IDE don’t work in that environment.
Now, if you want a better error message, try launching the IDE from a CMD or Powershell window. When the IDE crashes, you should get a text error message.
It’s a bit apples-and-oranges, but I have been able to run the Windows IDE on Windows 11 ARM from within a VM on an Apple Silicon Mac. Obviously YMMV on different hardware, but the emulation support worked fine in that environment.
If the IDE doesn’t work on Snapdragon, it might be something worth opening an issue for, but someone at Xojo would have to buy the hardware.
When Apple changed their Phone CPUs to 64 bit, snapdragon resisted, When it proved popular they followed suit. They’re a pretty conservative company that only seems to move when pressure makes them look bad. I wouldn’t be surprised if they are lagging considerably both in their chips and the MS support for them. I mean you have to consider that the M1’s are pretty old hat these days. especially compared with the M4’s. You’re likely comparing he snapdragon to M1 basic, rather than M1 Pro, Max or even Ultra.
The Xojo file fails to open and the IDE just disappears, whether started from the command line or not. No message on the command line or the screen. The IDE will still start by itself, but it looks like I have to start Mac projects over on the Snapdragon. I had a non-Xojo project for a few months, but now I’m going to start a few simple database projects over and see what happens. For real work (just simple little utilities mostly), I’m sticking to the Mac. The Surface is a wonderful laptop, but database support is lacking in every area, not just in Xojo.
After getting no results from running in the command window, I looked up how to generate a stack trace in Xojo, which seems to involve this code:
try
raise new RuntimeException
catch r as RuntimeException
MsgBox join(r.Stack, EndOfLine)
end try
I don’t know how to use it, however, and it doesn’t compile, which may be the point. There seems to be some question about enabling ‘include function names’ but the present consensus is that it doesn’t matter. For me, the results were the same either way.
Assuming this code works, where does it go and what is it supposed to do? I can’t get to the point where a message box appears. Is this still a thing that’s used. In the bug report pages I see people offering traces. How are they doing that?
I think that code is more about when you’re having a problem in a known area of your code.
I think you’re looking to use the App.UnhandledException event, and seeing what error may be occurring through there. The above is a sort of global event that fires whenever there is an error anywhere in your code that is not already caught in a Try Catch block.
In the above link, there is example code of how to display the error and the stackTrace. But I suspect from what you’ve described, this global error event may not fire because your app may not be fully launched yet. But it’s worth a try.
This UnhandledException code probably won’t fire on this Snapdragon at present because the IDE won’t open, but if I take it back to the Mac and pare the app down a little to the point where I could just open it for editing on the PC, putting this UnhandledException code in there might show me an error. It couldn’t hurt and it could only help going forward.