1. The ability to omit just part of a line from output. If you can just highlight part, using a regexp, then omitting also ought to be possible. This would be the big one for my list, and should be taken with a big helping of 'pleasepleasepleaseI'llloveyouforever'. I'm kinda trying to coax MUSHclient into being the uber-frontend for GS3, but unless I get this, there will *always* be control codes stuck in that I have to see even though I don't want to. Some of them, unfortuantely, end up embedded in text I otherwise do want to see.
2. A better interface for triggers/aliases/whatnot. Maybe make each group into a separate 'folder' or something. Once you get more than a few, it starts getting hard to deal with them.
3. I'd like the ability to change the color/font properties of Notepad windows, preferably on an individual basis. When I'm using them to catch chat output or something, I'd really rather have it using light-on-dark, not the dark-on-light that I use for text entry.
4. Possibly allow the infobar to actually be set to read *variables*, instead of just text, and update every time they change. It might (and I really don't know) be less clumsy to do that in the program code than to have a timer running every second to update it. Would make the infobar more useful for tracking changing numbers, like current health, whatever. I don't know, though.
And now, back to the miles of scripting that seem to be involved in this little project of mine. :)
> 2. A better interface for triggers/aliases/whatnot. Maybe
> make each group into a separate 'folder' or something. Once
> you get more than a few, it starts getting hard to deal
> with them.
Yes. I was noticing it myself. My suggestion would be to replace the existing structure with something like a treeview with triggers (as well as the alias list) being ordered like:
+Group a
||___Trigger 1 info
||___Trigger 2 info
-Group b
-Group c
...
It could be useful in some cases to also allow a Script subclass, but since not everyone uses a single script to pump data through from multiple triggers, it would likely be confusing for most people to have that.
> 4. Possibly allow the infobar to actually be set to read
> *variables*, instead of just text, and update every time
> they change. It might (and I really don't know) be less
> clumsy to do that in the program code than to have a
> timer running every second to update it. Would make the
> infobar more useful for tracking changing numbers, like
> current health, whatever. I don't know, though.
This is one advantage that ZMud has with its similar features. Auto-updating of some stuff would be nice, but with the current implimentation of the InfoBar it would be even less practical than it is now (especially when shared between worlds.) If you could set specific fields on the bar and have the contents of them returnable, then this wouldn't be an issue, but since different worlds can't share the same variables, you run into the situation of 'which' worlds variable updates it. Not a good thing...
Quote: This is one advantage that ZMud has with its similar features. Auto-updating of some stuff would be nice, but with the current implimentation of the InfoBar it would be even less practical than it is not (especially when shared between worlds.) If you could set specific fields on the bar and have the contents of them returnable, then this wouldn't be an issue, but since different worlds can't share the same variables, you run into the situation of 'which' worlds variable updates it. Not a good thing...
True. I don't use it between worlds, which does have a big effect on things.
1. The ability to omit just part of a line from output. If you can just highlight part, using a regexp, then omitting also ought to be possible. This would be the big one for my list, and should be taken with a big helping of 'pleasepleasepleaseI'llloveyouforever'. I'm kinda trying to coax MUSHclient into being the uber-frontend for GS3, but unless I get this, there will *always* be control codes stuck in that I have to see even though I don't want to. Some of them, unfortuantely, end up embedded in text I otherwise do want to see.
It could be possible to implement some sort of "line preprocessing" to handle stripping out, or changing, certain stuff.
Well, I just figure... if it's possible to turn a few characters yellow, shouldn't it also be possible to not display them?
As things stand, things can be somewhat frustrating because it seems like everything's geared at evaluating line-by-line... but sometimes what you want to affect is only part of a line. :)
OK, I see where you are coming from. Presumably this would be a regular expression, where only part of a line is coloured. The trigger would then have a "omit matching text" option. Is that it?
World.note would change the color of the whole thing. Turning it black might be an option for the moment, since it generally happens at the end of a room description, but removing it entirely would obviously be preferable.
And yeah, the bit with 'omit matching text' and using a regexp is exactly what I want. :)