After using the font, the IDE is ripe for reinstallation SOLVED!

[Petr]

Ide starts to freeze up terribly after using this font with the LoadFont command. The program runs normally with it, but since I used it, Ide is ripe for reinstallation (or is there a way to speed it up to its original values when entering commands and scrolling through the program?)
I only found out after I destroyed IDE 3.13.1 64X like this and now I have destroyed IDE 3.12.0 X32 anyway. 
Try it too (but be aware of the consequences for the IDE), after using this font - I recompiled and ran the program about ten times - and since then the cursor in the IDE has been stuck for about half a second if I hold down a button, for example backspace, so is deleted also that, what didn't want to delete.

Code: (Select All)

font = _LoadFont("PixelBookOut-Regular.ttf", 40, "monospace")

_Font font

[Petr]

Although I see that five people have downloaded the font (so I assume that one of them has tried it), there is no response. So, is it just my system that is having this problem, or is it happening to anyone else as well? I'm using Windows 10 (version 10.0.19045.5131)

[mdijkens]

If I understand you correctly, the IDE works very sluggish (scrolling, editing, etc.)
I suddenly had the same last week; turned out to be a windows update that made Defender scan my QB64pe temp directories again.
Had to exclude the QB64pe again from Defender

[Petr]

Man, you saved my nerves! Thank you so much. I never thought of that possibility (I was just wondering how the hell a font could do something like that). 
Thanks for the help, removing the folders from that Windows parody of antivirus helped. 

[bplus]

I have same crap happen when Opera is Updating too. Sorry I didn't pickup on it earlier.

It's almost ridiculous how often we misdiagnose a problem (for me anyway).

[Kernelpanic]

Man, you saved my nerves! Thank you so much. I never thought of that possibility (I was just wondering how the hell a font could do something like that). 
Thanks for the help, removing the folders from that Windows parody of antivirus helped. 

The problem has been mentioned here several times, including by me. These problems actually only occur when you use the so-called home directory under C:\\ in Windows.

Divide your HD into C:\\ and D:\\ and install executable programs such as QB64pe and the created QB programs under D:\\, and there are no more problems, not even with Windows Defender. At least I have never had any in this regard.

[JRace]

Yes, you can partition your drive as @Kernelpanic says, or even just create a new subdirectory for software installations - anything that keeps your software out of the root directory.  Windows has grown very protective of the root directory.

You can even use single-letter subdirectory names to make command-line work easier.

[mdijkens]

Man, you saved my nerves! Thank you so much. I never thought of that possibility (I was just wondering how the hell a font could do something like that). 
Thanks for the help, removing the folders from that Windows parody of antivirus helped. 

The problem has been mentioned here several times, including by me. These problems actually only occur when you use the so-called home directory under C:\\ in Windows.

Divide your HD into C:\\ and D:\\ and install executable programs such as QB64pe and the created QB programs under D:\\, and there are no more problems, not even with Windows Defender. At least I have never had any in this regard.

That's what I've always done; qb64pe lives here at D:\utils\qbpe64 from the start.
I think this time microsoft update decided to include it for some reason

[Petr]

Maybe it was true before, but I use three different versions of QB64 in parallel, two of which go to D: and one to C:, and the programs are placed on E: or D: as needed. Both IDEs started having the described problem regardless of which logical drive they were on. I excluded all folders related to QB64PE from defender and it's fine. I know it's been written here, but it's never happened to me before.
I'm currently investigating whether the necessary programs will run in Wine under Linux. I will definitely not tolerate this behavior of Windows under any circumstances.