"memory access violations".
I see this a lot. But never windowed.
If running full screen you can guarantee that it will happen 50% of the time when I first run my program.
I've put error reporting in every few lines, and Blitz appears to correctly create the window, and can e.g. report it's width.
But the next graphics call, even a Line call, will cause the error.
So much so, that I've had to hack into the runtime dll and replace the words "memory access violations" with "Problem, please restart the program" (which always works fine) - else what normal user is gonna know what m.a.v. means!
I see this a lot. But never windowed.
If running full screen you can guarantee that it will happen 50% of the time when I first run my program.
I've put error reporting in every few lines, and Blitz appears to correctly create the window, and can e.g. report it's width.
But the next graphics call, even a Line call, will cause the error.
So much so, that I've had to hack into the runtime dll and replace the words "memory access violations" with "Problem, please restart the program" (which always works fine) - else what normal user is gonna know what m.a.v. means!