PureBasic IDE Chokepoint

[oldefoxx]

I love many of the features in the IDE, for setting different fonts, size, color backgrounds, markers, and all that. I guess the downside is that the IDE becomes somewhat sluggish if you try to handle really large source files.

I tried pulling up the Win32API.INC file that I obtained from the PowerBasic web site. It's a pretty thorough reference of constants, structures, and API calls, but of course in the PowerBasic syntax. It took about 7 seconds for the IDE to bring it up on my PC (it is 1.42 MB in size). When I attempted to search for "DECLARE", it found the first occurrance fairly quickly, but then became unresponsive while it tried to find the next occurance, which is almost 91% of the way through the file. Yet WordPad and Word for Windows can find the second occurance in the fraction of a second.

So maybe I am asking for too much, but I'd like to see an IDE editor mode which would be more responsive when handling huge source files or
references, and maybe a way to toggle the bottom and size panels on and
off, so that you can see the main panel at max width when trying to read
the source code.

By the way, did PureBasic ever introduce a way to split up a long source
line so that it can be made into a series of shorter ones? Something like
the tagend underscore (_) allowed with some IDEs? And is there a
possibility that the Help could be extended to include a list of all predefined
#constants that PureBasic recognizes? (Not necessarily the ones that are
employed specifically for Windows APIs).

[Phoenix]

WordPad and Word are not applying syntax coloring which is why they're faster. Turn off syntax coloring in the IDE and it should load and browse the file as fast as them.

[Kale]

And is there a possibility that the Help could be extended to include a list of all predefined #constants that PureBasic recognizes?

Open IDE, Alt-S, and click on the constants tab.

[blueznl]

codecaddy will allow line continuation, but i seem to recall fred has promised it for a future version...

[Trond]

The problem with searching is a bug I think. Sometimes it uses ages to search in a relatively short document, sometimes it uses absolutely no time to find the search term.

[oldefoxx]

The tip about the Alt-S works, but where is it documented? You would expect to find some information on how to call up special viewers under Help, right?

[Trond]

It's in the tools menu.