Register forum user name Search FAQ

Gammon Forum

Notice: Any messages purporting to come from this site telling you that your password has expired, or that you need to verify your details, confirm your email, resolve issues, making threats, or asking for money, are spam. We do not email users with any such messages. If you have lost your password you can obtain a new one by using the password reset link.

Due to spam on this forum, all posts now need moderator approval.

 Entire forum ➜ MUSHclient ➜ Suggestions ➜ Reordering statusbar information

Reordering statusbar information

It is now over 60 days since the last post. This thread is closed.     Refresh page


Posted by Worstje   Netherlands  (899 posts)  Bio
Date Sat 18 Nov 2006 06:48 PM (UTC)
Message
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.
Top

Posted by Nick Gammon   Australia  (23,158 posts)  Bio   Forum Administrator
Date Reply #1 on Sun 19 Nov 2006 07:30 PM (UTC)
Message
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.

- Nick Gammon

www.gammon.com.au, www.mushclient.com
Top

Posted by Worstje   Netherlands  (899 posts)  Bio
Date Reply #2 on Sun 19 Nov 2006 08:04 PM (UTC)
Message
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!
Top

Posted by Nick Gammon   Australia  (23,158 posts)  Bio   Forum Administrator
Date Reply #3 on Sun 19 Nov 2006 10:06 PM (UTC)
Message
Well, maybe "More" should go first. What does everyone else think?

- Nick Gammon

www.gammon.com.au, www.mushclient.com
Top

Posted by Cino   Australia  (17 posts)  Bio
Date Reply #4 on Mon 20 Nov 2006 02:23 AM (UTC)
Message
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
Top

Posted by Nick Gammon   Australia  (23,158 posts)  Bio   Forum Administrator
Date Reply #5 on Wed 22 Nov 2006 04:24 AM (UTC)
Message
It is a great idea, I'll have to look into how easy it is to do.

- Nick Gammon

www.gammon.com.au, www.mushclient.com
Top

Posted by Worstje   Netherlands  (899 posts)  Bio
Date Reply #6 on Sun 03 Dec 2006 01:20 AM (UTC)
Message
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.
Top

Posted by Nick Gammon   Australia  (23,158 posts)  Bio   Forum Administrator
Date Reply #7 on Sun 03 Dec 2006 04:19 AM (UTC)
Message
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.

- Nick Gammon

www.gammon.com.au, www.mushclient.com
Top

Posted by Worstje   Netherlands  (899 posts)  Bio
Date Reply #8 on Sun 03 Dec 2006 10:20 AM (UTC)
Message
That is something I can live with perfectly. Thanks!
Top

The dates and times for posts above are shown in Universal Co-ordinated Time (UTC).

To show them in your local time you can join the forum, and then set the 'time correction' field in your profile to the number of hours difference between your location and UTC time.


20,790 views.

It is now over 60 days since the last post. This thread is closed.     Refresh page

Go to topic:           Search the forum


[Go to top] top

Information and images on this site are licensed under the Creative Commons Attribution 3.0 Australia License unless stated otherwise.