Yes. Just like that.

 

If .prg / wfm / ... has too many lines, we can't even change the code because it is very slow.

I have to edit the code in temporary .prg/... and then copy / paste.

 

And Source Editor Properties in "lightweight" configuration (see image)

 

This problem worsened markedly with dbase 2019 (13.x)

 

If the same file is opened and edited in Notepad++ v 7.x there is no problem.

 

 

 

 

"Gaetano"  escreveu na mensagem news:4w8ALtM0WHA.1876@ip-AC1E04A7...

 

 

This probably belongs to bug reports but I wanted to check if anyone was

noticing the same pattern before I post it there.

 

I was wondering why my computer fan was unusually loud and looked at the

program manager. dBase 2019 was on top of the list with a **permanent**

usage of 2.5-3.5% of CPU usage the moment I open a PRG in the source

editor without doing anything to it, even after minimizing dBase (with

focus on the Source Editor).

 

The usage drops any time the editor loses focus and the CPU cycles

increase with the size of the PRG file being open:

 

0.5-1% with a small PRG of just 80 lines.

 

2.5-3.5% with an 800-line PRG.

 

11-15% for a PRG of 5000 lines

 

20% for a 20,000 line PRG

 

I just copy-pasted the code of the previous file at the end of the PRG

for the last two samples as I don't have PRG's that large. The CPU usage

ramped up with every paste operation.

 

Give focus to something else, e.g. go to the Navigator, and the CPU

usage drops to normal idle levels of 0%-0.2%. Give focus back to the

Source Editor window and the usage goes up again.

 

Is anyone else able to reproduce this?