Wow! I get to post the 500th message.
Anyway, to get back with some of you about your questions...
Quote: "You could have an option to draw faint lines in different colors, at each indent:
| | |
If blah blah
| | |
| Do this
| And this
| | |
Endif| |
But only very faint, and have the ability to turn off"
It's one of those things I want to do sometime, but I just haven't looked into it enough yet.
@Frekster,
Sure, an option to turn off syntax highlighting will make it into the next version.
Quote: "
If so I'm guessing it would be a hassle to add some extra comments in the .dbpro and .dba include files to allow for individual text color settings to be saved in each file.
I realize it's kind of weird to want to color the syntax of different files differently, but with the way my eyesight is going sometimes watching the colors change as I change files makes it easier.
"
Hmmm, never thought about that, but it's certainly something for me to think about. I'm not sure if I could pull it off just using comments in a .dba file, but it might be possible to use the .dbpro file to store the information, as the DBP compiler seems to ignore anything that it can't understand.
Quote: "1 Just wondering, could you implement a function so that we can have the help file in a tab instead of a separate window?
2 Also so that you can move tabs about without having to close them all and opening in the order you want them."
The way the IDE is programmed right now, adding the help into a tab would be rather difficult as that's reserved for the editor control. However, it could easily be put into one of those dockable windows like the Code Explorer and Project Manager. I think I'll see if I can do that for the next update.
Quote: " BUG REPORT:
There are couple problem with the way CodeSurge identifies TYPES:
1. CodeSurge identifies TYPEs (in the Code Explorer) whenever it sees the word TYPE including if the TYPE statement is commented out.
2. CodeSurge identifies TYPE_AB ,which is a variable name, as a TYPE."
Ah, yes. It's all the fault of my lazy parsing routines. I've been wanting to fix it for several months now, but just haven't gotten me one of them round tuits.
Quote: " Found another way to break it.
* Pin the windows so they retract into the sides
* Close them using the x button
* go to 'View' and try and bring them back
Hope you can fix that as the fold-away toolbar thing is damn handy.
Thanks"
Thanks, Baggers.
I knew that there was a bug with the view menu not making the dockable windows reappear. However, I couldn't ever reproduce it because I didn't realize that it had to be folded away like that for the bug to appear. Just delete cssettings.ini to restore default settings. Now that I know more about this bug, maybe I can actually get it properly fixed.
Thanks again guys. Not sure when the next update will be as I have customers screaming at me to get their kitchens built right now.
Good performance is better than a good excuse.
CodeSurge -- DBP Editor for serious programmers.