The statusbar bugs me. It's got plenty of useful information in it, but the way I lay my window out hides most of it from me.
Sometimes, the window stops scrolling (quite a pain, I imagine this is due to some combination of gagging, echoing and stuff I do), and because my window is smaller, I don't see the [MORE/PAUSE] counter which isn't visible in my window. I'd love to be able to put it at the very left at least, to be like this:
[MORE/PAUSE] [Ready/custom script text] [world info] [world time] [BOX1] [BOX2]
(not sure what those last two thingies hold, actually.)
Being able to put those in any order and possibly hide some would be nice.
It is hard to reorder those boxes because of the way the MFC stuff was done in the source, however it would probably be acceptable if you could put the "MORE" thing in the info bar (above the status bar).
However it seems that you are the first person to ask for this, and the scripting interface does not currently expose the current "paused" flag.
I have added a new function to version 3.83 which will allow a script to query if the output window is paused, and thus update the info bar accordingly.
Haha, sorry about my excentric way of ordering my windows. I just don't see a point to having MUSHclient expose more than 80 lines horizontally if my mud will never output more than that in the first place.
However, if, at any time, you feel a desire of some kind to actually make the statusbar somewhat 'modifyable', it's very much welcome for two reasons:
1) Putting MORE in the infobar is a pain since I have different plugins that write to it, and one actually erases it each prompt. My infobar never has a 'fixed' location for information, which with MORE is kind of useful.
2) Other information, like my current world is stuff I'd love to forget about. It's already in the main window bar and only takes space at my statusbar. (I'm a sucker for clean, simple and powerful... what can I say?)
But this is a change I can work with none the less, even though I'll have to change half my scripts around. Kudos!
Well, maybe "More" should go first. What does everyone else think?
To minimise unused space, what about allowing the static status items to dynamically change size[1] when the window is made smaller[2] with a minimum length for each item determined by the current contents[3].
The items could begin to shrink at the point where currently they are cut off.
[1] like the writable status area
[2] e.g. for 80 columns wide
[3] or maximum expected; e.g. for lines, highest buffer size of all open worlds, or maybe this one should remain static
It is a great idea, I'll have to look into how easy it is to do.
I don't mean to bother, but I'm curious if there is any news on this? While GetInfo(..) is useful, it's preferably not something I'd like to rewrite 5+ scripts for to deal with using information the gui technically already displays itself... just outside of the window.
Having [MORE] foremost on the line would be the most perfect fix for small window users while I don't think anyone else is harmed by it.
Because of technical reasons (eg. the fact that the status bar stuff is done inside the Microsoft libraries) the best I can easily do is move the "MORE" item to be the first one after the generic status.
A quick test shows that this makes it still visible unless you resize the window to be quite small, so hopefully this will be OK for you, and still not confuse other users who are used to seeing the first entry (the generic status) be one that their scripts can update.
That is something I can live with perfectly. Thanks!