Change font size / Maintain screen size. - Printable Version +- QB64 Phoenix Edition (https://staging.qb64phoenix.com) +-- Forum: QB64 Rising (https://staging.qb64phoenix.com/forumdisplay.php?fid=1) +--- Forum: Code and Stuff (https://staging.qb64phoenix.com/forumdisplay.php?fid=3) +---- Forum: Utilities (https://staging.qb64phoenix.com/forumdisplay.php?fid=8) +---- Thread: Change font size / Maintain screen size. (/showthread.php?tid=1103) Pages:
1
2
|
RE: Change font size / Maintain screen size. - SMcNeill - 11-12-2022 Code: (Select All) Dim f(-1 To 0) As Long Simple code, and I can confirm -- it does indeed leak memory. Looks like it's something the team will have to look into. RE: Change font size / Maintain screen size. - SMcNeill - 11-12-2022 Note that the following does *NOT* cause a memory leak: Code: (Select All) Dim f(-1 To 0) As Long This must be some glitch which occurs in SCREEN 0 from the resize routine and how font is interacting with it. In 32-bit screens, there's no leak with memory with the above code. RE: Change font size / Maintain screen size. - SMcNeill - 11-12-2022 @Pete -- That's it! I've had it with your *voodoo snoodoo poopoo* glitches. Watch the video below and explain to me how the heck a program can behave in such a manner!! Pay close attention to the memory usage in task manager as the program does its thing in the background... You've broke what little brain I had left. What the heck type of glitch are you and SCREEN 0 pulling here? And why can't half the other people in the world seem to duplicate the process and run into the same issue?? Code: (Select All) Dim f(-1 To 0) As Long ^ Code used to generate the lovely little results we see above on my laptop. RE: Change font size / Maintain screen size. - Pete - 11-12-2022 Yeah, I'm on a roll today. Found something else goofy in the IDE, too. https://staging.qb64phoenix.com/showthread.php?tid=1109 Pete RE: Change font size / Maintain screen size. - grymmjack - 12-27-2022 (11-11-2022, 08:12 PM)MasterGy Wrote: You cannot use _printstring in hardware mode. Text output will be slow. If you include _display and use the font as a hardware image, it will be safer and much faster I can't figure out how to quote properly, if this looks funky I apologize. Sorry for posing this question (jeez am I Canadian? apologized twice already). Any way, do you have any examples of using hardware images? I tried to do it myself and it wasn't working. I was using the wiki example I think like this: Code: (Select All) SCREEN _NEWIMAGE(640, 480, 32) So many questions How does this LOOP UNTIL INKEY$ <> (a single double quote) even not register as a syntax error? But anyway, I just get a black screen on this. |