SDLIDE_for_BB4W updated

[Richard Russell]

I did the same on my Macbook Air M3 (Arm) running on Parallels and I think we can safely say it doesn't work under Parallels.

It would be interesting to know why, even if it's not easy to fix (if it's a Parallels bug they would probably like to know).

Since SDLIDE is a BBC BASIC program you should be able to debug it and find out exactly what is happening. If you can spare a few minutes, please do that.

Edit: I should add that SDLIDE.bbc will of course be a slightly different version from what's in SDLIDE_for_BB4W (1.41a rather than 1.41b) but that shouldn't be relevant from the point-of-view of tracing the Parallels incompatibility.

[Leo]

Hi Richard,

Your update to SDLIDE_for_BB4W has fixed the problem I had - thank you very much for that.
Regards
Leo

[Richard Russell]

Your update to SDLIDE_for_BB4W has fixed the problem I had - thank you very much for that.

It was an 'interesting' experience! One of the big strengths of libraries, as opposed to inline code, is that you can fix a bug in a library and that fix will automatically be picked up by any program which uses that library.

But unfortunately it can work the other way too. If you somehow contrive to have an out-of-date library on a PC, as I did, all the programs which use that library suffer equally - and in this case fail in quite a major way.

It's not a problem I have encountered before, because all my development and release builds have been done on the same PC, but with the Code Signing dongle issue that is unfortunately no longer the case.

It shouldn't be a problem with BBCSDL, because the libraries here are stored in a folder which is synchronised between the PCs by OneDrive. But the BB4W libraries are in C:\Program Files (x86)\ which isn't synchronised.