Forums » Suggestions
Programming aids
It seems Vendetta reorders the "wgaf.cfg" file (by alphabetical commands like "alias" then "bind" then "set").
This is somewhat anoying but as a software developer myself I can see how this happens: runtime efficiency when parsing the console commands and rewriting the file to disk when using the game command system to edit the file.
The result, though, is a quickly messed up file where command lines (binds and aliases) are shuffled to a point where one can not make sense of some sequences.
I would like to keep my bind programs organized, and one way would be to have some sort of "include" command:
#regular wgaf.cfg commands here
...
include [fullpath/]mygaf.cfg
where an optional full path would let us put these files anywhere we want (quite frankly, within the application bundle is not the best place for Mac OS X users).
The mygaf.cgf file would be of the same format as the regular wgaf.cfg file, but because Vendetta wouldn't thinker with these commands (unlike some in the regular wgaf.cfg file), it's content would not get reordered.
This would make it easier to group related commands and maintain them.
Perhaps, too, a "/reinit" command to refresh the commands if you happen to edit these files while Vendetta is running (indispensable if you ask me when trying long sequences).
Another programming aid I'd like is "/debug [0|1]" wich would simply "echo" every commands as they are executed. With , as necessary, some sort of error result reporting if it applies (aka "unterminated single/double quote error" and the like).
This is somewhat anoying but as a software developer myself I can see how this happens: runtime efficiency when parsing the console commands and rewriting the file to disk when using the game command system to edit the file.
The result, though, is a quickly messed up file where command lines (binds and aliases) are shuffled to a point where one can not make sense of some sequences.
I would like to keep my bind programs organized, and one way would be to have some sort of "include" command:
#regular wgaf.cfg commands here
...
include [fullpath/]mygaf.cfg
where an optional full path would let us put these files anywhere we want (quite frankly, within the application bundle is not the best place for Mac OS X users).
The mygaf.cgf file would be of the same format as the regular wgaf.cfg file, but because Vendetta wouldn't thinker with these commands (unlike some in the regular wgaf.cfg file), it's content would not get reordered.
This would make it easier to group related commands and maintain them.
Perhaps, too, a "/reinit" command to refresh the commands if you happen to edit these files while Vendetta is running (indispensable if you ask me when trying long sequences).
Another programming aid I'd like is "/debug [0|1]" wich would simply "echo" every commands as they are executed. With , as necessary, some sort of error result reporting if it applies (aka "unterminated single/double quote error" and the like).
You mean like /load configfile (we already have this)...
Doh!
I didn't see this one in my list.
But can I specify a full path?
I didn't see this one in my list.
But can I specify a full path?
I think you can.