[IDE] Progress when loading sources

[Inf0Byt3]

It would be great if the team had the time to implement a small progressbar in the statusbar of the IDE for use when loading big source files. It would make the IDE more responsive. This isn't a big issue, as the IDE is already fast - takes only 2-3 seconds to load a 800kb source, but it would make it look a bit better. Thanks.

[nospam]

It would be great if the team had the time to implement a small progressbar in the statusbar of the IDE for use when loading big source files. It would make the IDE more responsive. This isn't a big issue, as the IDE is already fast - takes only 2-3 seconds to load a 800kb source, but it would make it look a bit better. Thanks.

Buy an SSD instead. My machine loads 400 preferences into a structure and a 3.2MB file into 222 distinct PB arrays in under 600 milliseconds. Who needs progress bars?

[Inf0Byt3]

Buy an SSD instead. My machine loads 400 preferences into a structure and a 3.2MB file into 222 distinct PB arrays in under 600 milliseconds. Who needs progress bars?

Sure, but the hard-disk isn't the bottleneck here . If anything, it's the CPU (probably related to Scintilla parsing the code, highlighting it, etc.). My request is related to the way PureBasic behaves while loading the source, the fact that it doesn't respond, not the fact that it takes x amount of time to load it.

And then why did Microsoft add progressbars in their IDEs?

[nospam]

Sure, but the hard-disk isn't the bottleneck here . If anything, it's the CPU...

Oh, yes, I forgot about that. I also have an Intel i7-3770 CPU.

And then why did Microsoft add progressbars in their IDEs?

To make sure that you always had a reminder right in front of your face that you needed to upgrade your hardware.

Anyway, I'll shut up now. I don't have the problem you mention and I can't add any value.

[srod]

Mine shows quite a lag sometimes, but then I do load some very large source files and I do have the slowest laptop on the planet!

[Danilo]

Loading a 350kB include file with 9.000 lines of code only can take up to 6-7 seconds here (IDE showing busy cursor).
I think parsing+highlighting takes much more time with extensive macro usage.