Vyzor, UI Manager for Mudlet

[Oneymus]

I swear it's some error on my end, but I've tried it any number of ways and the only way that worked for me was dropping it directly in C:\ (symlink and copy both worked for me).

For now, I am assuming it's some quirk of Windows 7's permissions systems; they're almost always responsible for strange behaviour on Win7.

[Daagar]

Loving this package so far Oneymus. I have a few silly questions though. These are going to be obvious when I hear the answer, but humor me:

* How do I force vyzor to be first in the 'scripts' panel? Each time I load mudlet, things get resorted alphabetically (vyzor ending up at the bottom, as you might expect). I have to manually resort to get dependent scripts to compile.

* How do I force a full 'reset'? As I'm tinkering, I add/remove/resize frames, gauges, etc., and I can't seem to get them to clean up. This is especially true if I create a test frame and later remove the code for it without having done an explicit frame:Remove() - I have to restart mudlet to start fresh.

* What's the right way to be using gauge:Echo()? I can set the text on my gauge just fine, until the first gauge update then it reverts back to the default text.

[Oneymus]

* How do I force vyzor to be first in the 'scripts' panel? Each time I load mudlet, things get resorted alphabetically (vyzor ending up at the bottom, as you might expect). I have to manually resort to get dependent scripts to compile.

I don't remember experiencing this problem, but it has been a while since I've dealt with a great number of Scripts at a time. It surprises me that this would be normal behaviour, given the potential for complex script interdependence. That being said, if it's a persistent problem, you should be able to drag Vyzor into a folder named "aa" or something similar.

Alternatively, put your GUI script in the Vyzor folder itself.

When Vyzor is added to Mudlet, this should be a non-issue.

* How do I force a full 'reset'? As I'm tinkering, I add/remove/resize frames, gauges, etc., and I can't seem to get them to clean up. This is especially true if I create a test frame and later remove the code for it without having done an explicit frame:Remove() - I have to restart mudlet to start fresh.

There is a function called resetProfile(). I've never had success with it, but it's supposed to remove all labels.

Additionally, for Vyzor specifically, there is a line commented out in the current Script that loads everything that will remove the package completely. This simply calls the alias "U".

* What's the right way to be using gauge:Echo()? I can set the text on my gauge just fine, until the first gauge update then it reverts back to the default text.

By setting the TextFormat of a gauge, you can make it echo custom text every update. Be sure to include two wildcards (I use %s) for the two numeric values. Right now, the default is: "<center>%s / %s</center>".

If you set AutoEcho to false, it won't re-echo every update, allowing you to handle your own echos if you'd prefer to do it manually.

If this method seems strange, I am open to suggestions.

[Heiko]

* How do I force vyzor to be first in the 'scripts' panel? Each time I load mudlet, things get resorted alphabetically (vyzor ending up at the bottom, as you might expect). I have to manually resort to get dependent scripts to compile.

This is not a problem in the regular Mudlet releases so I assume that you use a modified version of Mudlet.

[Daagar]

I use chris' git version of mudlet with module manager support, so it could be related to that somehow. Not a huge deal, as mentioned I can rename the package if need be ( I haven't quite mastered how the module manager works anyway ).

Setting the TextFormat was exactly the solution I was trying to achieve with gauge:Echo. So not strange at all, I just didn't understand the right way to do it.

Both resetProfile() and the full unload/reload of Vyzor via the 'U' alias seem to behave... oddly at times. Yet other times it works as expected. Pretty sure it is the order of things happening, and my hack gauge code

Vyzor is great because of the automatic resize support. I frequently switch between two screen sizes, so that feature is absolutely critical to making something usable. Huzzah!

[Oneymus]

Vyzor is great because of the automatic resize support. I frequently switch between two screen sizes, so that feature is absolutely critical to making something usable. Huzzah!

I like hearing that, as that was one of the primary motivations for the work on Vyzor.

Thanks!

[Vadi]

* How do I force vyzor to be first in the 'scripts' panel? Each time I load mudlet, things get resorted alphabetically (vyzor ending up at the bottom, as you might expect). I have to manually resort to get dependent scripts to compile.

This is not a problem in the regular Mudlet releases so I assume that you use a modified version of Mudlet.

Modules are reinstalled on every profile load, and thus appear at the bottom. The list isn't actually re-sorted.

[Daagar]

Thanks, that just dawned on me a little while after I posted (and when I noticed that vyzor was being reinstalled when I restarted - d'oh!)

[Vadi]

Yes. What Vyzor should instead do, and this is a pattern I've made with my system as well, is raise an event for when it's loaded - and your scripts can hook onto the loading event to initialize.

[Oneymus]

Yes. What Vyzor should instead do, and this is a pattern I've made with my system as well, is raise an event for when it's loaded - and your scripts can hook onto the loading event to initialize.

I can definitely do that.