PureBasic Forums - English

Hi at all.

I have a big project. About over 32000 lines of code spread over 25 files (24 includes and 1 main file).
Since I hit the 30000 mark - inserting a new line becomes very slow. It takes nearly 1 seconds
That's horrible long if you are fast in typing
Everything else runs fine without problems (autocomplete, ...).

I think the IDE checks for procedures, macros, variables, ... after each new line (my thoughts) ... and that's it why it
becomes slow.

Is there a way to speed this up? A workaround?

If not, maybe it can become a feature request -> a checkbox in the settings, not to recheck all code files?!?

My system: Win 7 Prof (x86), Intel Core2 Duo @ 2,94 Ghz, 4 GB RAM, PB 4.51

Greats, Morty

Occasionally I have the same problem. Most times the IDE responds as fast as it should and other times it is really slow: Typed characters appear about a half second later and generally editing the code is a huge pain. I think it happens when the IDE is opened for a longer time but I'm not sure about it because it just happens every now and then.
However, I was always able to fix it by restarting the compiler or closing the IDE and opening it again.

I have found a tremendous increase in the IDE speed after turning off cleartype and antialiased font rendering in the control panel. But this was on XP, maybe ClearType is faster on Windows 7. Also it seemed to be related to long comments.

Trond wrote:I have found a tremendous increase in the IDE speed after turning off cleartype and antialiased font rendering in the control panel.

Turned them off in XP itself, or somewhere in the IDE??

kenmo wrote:

Trond wrote:I have found a tremendous increase in the IDE speed after turning off cleartype and antialiased font rendering in the control panel.

Turned them off in XP itself, or somewhere in the IDE??

In XP itself.

well the solution to your problem is http://editplus.com

you can edit how much you want,
don't forgot: you must download user files for purebasic syntax (color style) .

Split it into one file per major function or system. This way you will have 30 files thats 1000 lines of code and a better structure in the end.
Let your main.pb only be

includebinary "networkfunctions.pb"
includebinary "graphicfunctions.pb"
includebinary "show_as_table.pb"
includebinary "export_to_excel.pb"
includebinary "mainloop.pb"
mainwindow_open() (which is a procedure somewhere to open the main window
repeat
mainloop()
forever

I like to expand this question a bit - how can we speed up the compiler.
Don't get me wrong. Its really fast as it is, compared to M$ where you can go get a cup of coffe before its done. I've noted its much faster on my MacBook Air than my more powerful Windows based machine. I don't think this is because Xcode is efficiant, I think it has to do with the disc.
Are there any files that can be temp:ed in a Ramdisc during compile? NASM? Output file to ramdisc?

To speed up the compilation process you could split your projects into different libraries (DLLs).
That especially makes sense for tasks that are completely different, so if you're writing a game you
could split up the sound engine and the graphics engine into libraries.