Bad news - The syntax highlighter has hit a wall. Apparently, its operations are parsed by the RichTextBox control's undo/redo manager, meaning the highlighting can be undone with Ctrl+Z. Looks like its going to get dumped for the moment. I'll release the beta without the feature. It'll probably stay that way until I switch to a custom text editor.

It's a shame the syntax highlighter isn't working as expected. But it still looks awesome! :celebration:

Would it be possible to have something that marks mis-matched paranthesis? Not a major thing, obviously, but when you're doing a lot of them it's easy to miss one, and then annoying to go back and look through 600+ lines of Script for the one that's wrong...

I even added a few shortcut keys :

Ctrl+Space - Focuses the common edit textbox ( the one you see at the top )
Ctrl+F (when focusing the said textbox) - Find
Ctrl+H ( " ) - Replace
Ctrl+G ( " ) - Goto Line

I don't think it can get more counter-intuitive than this!

OBSE catches those as it is.

I was thinking about perhaps adding an imports/include feature that'd let the script writer to easily add common or frequently used blocks of code. Something that would work like this:
The user adds an import/include command that follows the working of the #include directive in C/C++ :

scn test#include "CommonQuestVariables"begin gameMode   let fQuestDelayTime := 0.001   let sWorking := 1end

whose parameter is the name of a text file present in a fixed directory (Data\Scripts or Data\Imports) :

float fQuestDelayTimeshort sWorkingfloat fEndianess

When compiling, the line gets replaced by the contents of the parameter:

scn testfloat fQuestDelayTimeshort sWorkingfloat fEndianessbegin gameMode   let fQuestDelayTime := 0.001   let sWorking := 1end

Would such a feature be useful ?

OMG, YES!

[edit]
Too bad indeed of the syntax highlighter, it has always been a valuable asset to me. Hope you'll find a way to make it work in the future.
[/edit]

Come now, that counts as spam!

I should have picked up an existing text editor control instead of writing one from scratch - That way I'd have save me a lot of work. For some strange reason, it only occurred to me after having coded most of the editor. But then again, had I used a preexisting editor, I wouldn't have gained any experience with C++\CLI.

Really? I never knew... (I'm sure I've had issues even with it...) but no problem

Wow, this looks really neat - particularly the function auto-completion. Nice job shadeMe!

What do you think about implementing simple use of the #define command as well as #include? Sometimes it's useful to reuse the same value throughout a script, but there isn't really any point in storing it in a variable.

Translating shorthand assignment operators could be pretty useful to, so things like this could be used:

fTimer += GetSecondsPassed

Cipscis

RegEx?

I was thinking about the same. Will do.

OBSE's let command already supports such compound operators.


Not at the moment. But it shouldn't be hard to add support for RegEx.

Oh ok, I guess I'm really not up to date with what OBSE is capable of.

Cipscis

You know what I thought - an auto completion feature like when writing an if statement and pressing enter an endif is added and the cursor appears, indented by a tab (ini set), between if and endif lines -same with begin - the way braces autocomplete in some editors
Dunno if possible but it would be rather handy

Well, auto-indenting does some of what you've suggested. With it turned on, all you have to do is hit enter - The indentation is taken care of by the editor. The workflow goes like this:

• begin gameMode
  
• 
  
• if (1)
  
• 
  
• Add more code
  
• endIf/else/elseIf
  
• 
  
• 
  
• end
  

While it might not add the closing statements automatically, it doesn't interrupt your pace by requiring you to scroll past those line. Personally, I feel that this is a better option.

Have to try it out - never worked with such an editor
:tops:

This all sounds good, but one thing I really like about VC++'s auto-indentation is that if you return twice (i.e. leave a line blank), it removes the tabs from the empty line. It really irks me to have the empty tabbed lines in there for some reason. I actually go and remove them when I'm working with auto-indentation that doesn't do that... yeah, that's kind of OCD, I agree...

Easily done, but then again, since when did you start using the CS ?

I have to test my functions, you know.

Plus ARES is about 40% CS work anyway. So you really want me in the CS.

Your wish has been granted. Any other features you'd like to request ?

RegEx, auto-indentation, and a persistent font? It's all I could have ever wanted!

Out of curiosity, how are you doing the auto-complete? Does it use the CS's function list (i.e. the one that OBSE adds functions to, and therefore guaranteed to include all relevant functions), or is it a hard-coded list? It'd be pretty neat to have it automatically include all functions from the CS, OBSE, and loaded plug-ins. No idea if that's possible.

Hmm, what about setting up inter-plugin messaging (the OBSE messaging API supports this) that allows plugin authors the ability to specify some kind of generic URL to which the function name could be appended to produce a link to the documentation? Like for OBSE commands, you could use http://obse.silverlock.org/obse_command_doc.html#, and then any function name appended to that will be the URL for the exact command in the Command Document? Or say, if I have NifScript's functions listed at http://cs.elderscrolls.com/constwiki/index.php/NifScript/ plus the function name, I could have a Message set up in NifScript to give that URL to your thing so that people could look up the documentation on NifScript functions. Could even work on people's personal web sites, provided they use a naming scheme that works as described...

EDIT: Haha auto-parser, haha. You win this time.

I'm currently using a custom list that was created using OBSE's DumpDocs command (slightly modified to strip out the stuff I don't need). I did consider the possibility of parsing loaded CommandInfo objects but was unsure how to (not even sure if the struct is used by the engine or if its just glue). I've popped the question to scruggsy and am awaiting a reply.

Already present (kind of - You can right click on any token in the script text and directly look it up on either the wiki or the OBSE command doc through the context menu. Command doc linkage is the same as your suggestion. Wiki look up uses the search function).

Search function is a good idea, but uh. The Search function's kind of notoriously bad. So I think it would be nice if plugin authors could 'cut out the middle man', so to speak, and just tell your tool where to find the information.

That's true. I guess I'll experiment with the messaging API then. But before I start, what do you think if using Google instead ? A simple site:cs.elderscrolls.com identifier in the search string can get us to use its prowess instead.

But then that just leaves you with a Search page, which is sort of less-than-helpful. Unless you can somehow trigger the I'm Feeling Lucky button that way? Of course, the chances of getting the wrong thing might be pretty high...