12-30-2022, 05:10 PM
(12-30-2022, 07:21 AM)mnrvovrfc Wrote:(12-28-2022, 02:42 PM)TerryRitchie Wrote: Ok, that's an odd one. Line 3622 simply unloads the font from RAM:This statement has been unreliable since its creation. In particular the programming system complains when the programmer tries to release the font it thinks is active...
_FREEFONT Font
I believe you need to have any surfaces that the font has been assigned to removed from RAM before the font can be removed. In the options subroutine I create a screenshot and I believe that screenshot inherits the font. When the user presses ESC while in the options screen that screenshot is still sitting in RAM and hence the error. I'll need to rework the code to remove that screenshot to account for this.
I've never had a problem with any of the font commands over the years, including _FREEFONT. I've just found a certain order of operations needs to be adhered to when using them. I used to think this was an SDL thing but this same behavior occurs on the latest versions of QB64 as well.