InfoBar/Status Bar

Posted by Hoss on Fri 26 Nov 2004 08:39 PM — 3 posts, 16,222 views.

USA #0
Hey I'm working on something with my info bars and the such and I want it to display different information the only problem I'm getting is that with the info bar it keeps stacking so instead of just showing something like:

You have no venoms secreted

it will show after alittle while:

You have no venoms secretedYou have sumac secretedYou have no venoms secreted

Anyway beside having to clear it everytime that I could have it just get rid of the older messages? Also I was wondering if there was a way to create another info bar or something else like it? Incase that's not clear enough I want it so I can seperate the status bar or something like that so I can have the a section on my venom situation and then on the right and maybe a section about my gold situation on the left?

Thanks

Hoss
USA #1
You can only have one info bar (you can use the status bar, although its not comperable).

No, you cant get the text from the info bar.

What you COULD do, is have two variables, strings, that have information on your two statuses (venom and gold) and then you'd edit one or the other, then clear and set the info bar (with BOTH variables).

That way, you'd always have both things updated, theyd update at seperate times, but you'd know what the other was with the variable.
So really, you'd know what was on your infobar, even without being able to get it.

(I suggest a seperate sub for writing to the bar, then you could get fancy with it, with minimal bloat, fancy being adding X spaces between the end of the first and the second (to get a constant location for the other bars, where X is n-[the length of the first string])).
USA #2
Actually, if you knew what you where doing you could use the main windows handle (available through scripting) and a language like Python to link to the InfoBar itself and read the text from that. But you would have to know what you are doing. Frankly, with the scripting where it is now, there is almost nothing you couldn't manage. Though figuring out how is a major issue, which is why having some things like the extended window functions Nick is working on is still a lot more reasonable than trying to do it the hard way and risk crashing the client in the process. (Not to mention the problem that scripts can only read or change the contents of Mushclient's windows when they have access to that handle. They can't recieve button clicks or other things. At least not in any way I have been able to figure out.