[discussion] Cs Script Editor Wish List : IV - Oblivion

» Tue Mar 15, 2011 12:35 am

I read through the named ones at the top, but there are so many other replies I did not read through the responses. So sorry if this has already been named (or I miss read the ones posted at the top) but I would like a "Did you mean?" function. Whenever you put a invalid or incorrect function it is gives a recommendation of a correct function.

Well, IntelliSense does suggest command and variable names as you type.

» Mon Mar 14, 2011 10:10 pm

WOW this will definetly help all scripters I have a good scripter friend i am sure can offer some suggestions I'll tell him hope this is done soon...COOL

» Mon Mar 14, 2011 6:55 pm

Have implemented Bookmarks and the "Last Known Caret Position" feature requested by spookyfx. Both are stored as directives in the script itself.

» Tue Mar 15, 2011 2:51 am

What features would i like to see?

Support for OOP, project management, support for multi-threaded scripts, support for encapsulation - inheritance - and polymorphism!

Perhaps i went too far...

» Mon Mar 14, 2011 4:15 pm

What features would i like to see?

Support for OOP, project management, support for multi-threaded scripts, support for encapsulation - inheritance - and polymorphism!

Perhaps i went too far...

Well, you missed metaprogramming.

» Mon Mar 14, 2011 3:47 pm

Well, you missed metaprogramming.

Touché my friend, touché...

» Tue Mar 15, 2011 5:04 am

Before anything else let me start by thanking you for creating this, i am sure its going to be excellent.

A feature i would like is the possibility of saving while the script editor is open. I ask this because i always have to try my scripts like a thousand times before getting them right, and every time i have to close the script window, save the plugin start the game and later open the script editor again and search for the script. It may not seem like a big deal but when you do this 10 or 20 times in a row it can get tiresome.

» Mon Mar 14, 2011 6:07 pm

A feature i would like is the possibility of saving while the script editor is open. I ask this because i always have to try my scripts like a thousand times before getting them right, and every time i have to close the script window, save the plugin start the game and later open the script editor again and search for the script. It may not seem like a big deal but when you do this 10 or 20 times in a row it can get tiresome.

There is actually a vanilla INI option that fixes that. Search for Useful Construction Set INI Settings on the Wiki.

» Mon Mar 14, 2011 7:53 pm

The command table is now read from the memory. On to the esm/esm reader!

» Mon Mar 14, 2011 1:02 pm

some sort of save or error confirmation would be nice. it's a real beginners trap when you click save, but the script doesn't save and no error pops up, and you close it thinking it has saved. happens with certain errors

» Mon Mar 14, 2011 5:52 pm

some sort of save or error confirmation would be nice. it's a real beginners trap when you click save, but the script doesn't save and no error pops up, and you close it thinking it has saved. happens with certain errors

Some syntax error which cause that behaviour are handled. OBSE's preprocessor should handle the rest (or at least its better part).

» Mon Mar 14, 2011 1:02 pm

Some syntax error which cause that behaviour are handled. OBSE's preprocessor should handle the rest (or at least its better part).

that's good, it catches me out so many times :brokencomputer:

» Mon Mar 14, 2011 6:50 pm

So I'm totally not reading the rest of the thread before I post this feature request.

I would love to be able to jump from a Call function directly to the function script. Formulator is approaching 200 scripts and I'm starting to lose track of what's still not actually implemented.

In fact, better still if you can store your own metadata would be a little checkbox for function scripts: "Not Fully Implemented." That way calls to them would compile, but could be turned red (or whatever) as a reminder.

» Mon Mar 14, 2011 1:56 pm

So I'm totally not reading the rest of the thread before I post this feature request.

I would love to be able to jump from a Call function directly to the function script. Formulator is approaching 200 scripts and I'm starting to lose track of what's still not actually implemented.

In fact, better still if you can store your own metadata would be a little checkbox for function scripts: "Not Fully Implemented." That way calls to them would compile, but could be turned red (or whatever) as a reminder.

Jumping into function scripts has been on the agenda for awhile now. In fact, IntelliSense stores variable and function metatdata in its database. For example, take the following function:

scn zzTestFS; function description; more text; NOT IMPLEMENTEDfloat fExtra   ; Extra datastring_var svEntryPoint   ; Entry point nameref rTarget    ; Target actorbegin function { svEntryPoint rTarget fExtra }   ; codeend

When you type in call and hit a delimiter, the ISense box pops up with the names of defined functions. Selecting an option would show a tooltip along the lines oft:

User Function
zzTestFS

function description
more text
NOT IMPLEMENTED

3 arguments:
Entry Point name [String Var]
Target Actor [Ref]
Extra Data [Float]

Double clicking on a call statement should also bring up the subsequent UDF's tooltip. Good enough or have you got suggestions ?

» Mon Mar 14, 2011 6:38 pm

Good enough or have you got suggestions ?

Definitely will serve. My wish list item would be a way to flag something that's visible without having to actually click on the function... a tag that lets you set the color of the text, for instance. So I don't have to go through clicking everything to know if I missed one.

» Tue Mar 15, 2011 4:15 am

Definitely will serve. My wish list item would be a way to flag something that's visible without having to actually click on the function... a tag that lets you set the color of the text, for instance. So I don't have to go through clicking everything to know if I missed one.

While assigning color to text is quite possible, it got one nasty quirk - It can be un/re-done with the Ctrl+Z/Y key combo. This was actually the reason why I dropped syntax highlighting. I could fix that by painting the text manually but that would probably require a rewritten implementation of the renderer; something I'd rather avoid.

You can however use bookmarks as a workaround, as marked lines numbers are colored differently.

» Mon Mar 14, 2011 1:06 pm

Edit: Wrong thread.

» Mon Mar 14, 2011 6:29 pm

This is coming along rather quickly, can't wait to try it all out. Any ETA on a beta/alpha?

» Mon Mar 14, 2011 2:43 pm

This is coming along rather quickly, can't wait to try it all out. Any ETA on a beta/alpha?

I'll probably release the beta after I'm done with the plugin reader. It'll need a newer build of OBSE to work, meaning it'll stay in beta until OBSE 18a is out.

» Mon Mar 14, 2011 1:48 pm

I would be happy to get a "compile all" command only for an activated plugin.

» Mon Mar 14, 2011 7:21 pm

I would be happy to get a "compile all" command only for an activated plugin.

Might be possible. I'll look into it.

Some good news: I recently discovered a couple of functions that could greatly improve IntelliSense, among other things. For instance, the editor can now look up remote variables on any valid reference.

» Tue Mar 15, 2011 2:41 am

IntelliSense is less stupid now - It supports variable list lookup for scriptable forms, http://i659.photobucket.com/albums/uu320/shademe/Untitled-63.jpg, suggests quests and local variable names when using assignment functions and can tell which functions need a calling reference.

Preprocessor macro are less limiting now and allow most delimiters in their value fields.

» Mon Mar 14, 2011 10:47 pm

How about displaying the script's current character count & character limit and the compile size (as of the last compile) & compile size limit? Would be handy to know when you're approaching the limits and need to consider condensing or splitting it across multiple scripts.

» Mon Mar 14, 2011 7:22 pm

How about displaying the script's current character count & character limit and the compile size (as of the last compile) & compile size limit? Would be handy to know when you're approaching the limits and need to consider condensing or splitting it across multiple scripts.

Compiled size won't be an issue as I'll be going through the bytecode anyway, for the offset viewer. But why bother with character limit when it's been removed ?

» Mon Mar 14, 2011 8:54 pm

Ah, good point. That was a brain fart on my end...I was thinking in terms of the vanilla limit. There might still be a use for it in terms of the that limit to note the scripts that don't use OBSE commands but still require OBSE to compile.

Also, I may have been wrong about OBSE removing the limit all together. It likely just increased the limit to a higher and harder to hit value.

Would have to asks scruggs, or go digging through OBSE's source to be sure :shrug: