No crash in Windows XP even with _LIMIT commented out. I assume you're on to a fix to it, Steve?
I was curios as to why the 'limit' was put there... Experimented a little and figured it was to 'slow' the process... Left the 'limit' commented out and inserted a '_DELAY 0.1' before the '_FREEFONT' and it worked just fine.
My theory is: The font is being loaded... QB64 does its thing... _FREEFONT is encountered, possibly before the 'load' has finished, and promptly dies because there is no font to 'free'.... Just a guess... Thoughts?
ScaleScreen? My older version does not support ScaleScreen. What is it?
Pete
Ah, it looked like the code ended at the SLEEP statement. I was wondering why ScreenScale wasn't _ScreenScale if it was a new keyword. Anyway, I gave it a run and it worked fine. I'm running QB64 v 1.1 from September 2016 on a Windows 10. I actually have a more current version on my Win 7, but it is away at a resort for a well deserved rest.
Pete
Interesting that if I change to _LIMIT 1, it doesn't crash, but the window just stays open and nothing prints to it. Key presses have no effect. If I change to _LIMIT 10, it completely crashes. _LIMIT 25 works.
Pete
I'm still stuck on why the auto-run code I put in the last code box post won't work.
I can get your original program to run without _LIMIT 25 if I add a delay after line 2.
As I mentioned on the previous page, it's a _LOADFONT issue. All you need to see the issue is:
FOR I = 1 TO 100
F = _LOADFONT("cour.ttf", i, "monospace")
NEXT
print i; " ";
_freefont F
Hi
please with what QB64IDE version is the issue coming out?
I've got a very different experience in my TOSHIBA i3 4GB RAM Windows 10 e QB64IDE version 1.2 revision [dev build] from git e490b1a !