Configuration window improvements

Hiya,

I like MUSHclient a great deal, particularly due to its scripting abilities (thanks!). There's one thing that drives me batty on a daily basis though: the configuration window.

I use it a -lot-, specifically to change aliases and triggers. Two changes would make things a lot nicer for me:

a) Make the configuration window resizeable (preferably maximizable), so I can see more triggers or aliases and their send data at once. I have dozens of each right now, and it looks like it's going to become an order of magnitude larger before long. The current window shows too little to be of much use.

b) Could the config window please -not- lock up the main window? It would be very nice if I could change a trigger without closing the main config window, hit alt-tab, give the trigger a test, then alt-tab back to make any further changes.

What's happening right now is that if I want to change a trigger or alias, first I must open the proper config window, hunt down the appropriate trigger or alias, edit it, close everything, test, then open the proper windows again, hunt for the proper trigger or alias all over again, edit it, et cetera.

It's a minor usability issue, but it'd make a large difference for someone like me who uses it constantly. I hope you'll consider it.

Ah, any maybe a couple more suggestions:

c) Could we change the order of the titles in those windows and have them stick? For example, I'd like "Label" to come before "Trigger", since most of my triggers are a noise of regex.

d) Remember which trigger or alias we last had selected between config windows? If I open the triggers window, chances are I'm interested in the same trigger I was last editing, or something nearby, so it'd be nice if it was already highlighted.

First, you can change the order of the titles, by dragging them to a new position.

If you have lots of triggers you may want to investigate the "filter" functionality. There is an example filter shipping with MUSHclient, but you could write your own that lets you (say) enter a string in a dialog box, and only show triggers whose name/match text/something match that string.

> First, you can change the order of the titles, by dragging them to a new position.

Ah, my fault. It didn't work under Wine, and I just assumed.

I hope you'll still consider a), b) and d), at least if they're also not problems caused by Wine.

I'm not sure about the resizing, this is a dialog box, and resizing is fiddly because all the buttons have to move.

Similarly, to make it a modeless dialog box (ie. that doesn't lock the main window) requires a major change. Also, modeless dialogs tend to disappear under the main window and get forgotten.

Remembering the last thing edited is a nice idea, I'll look into that.

As for the filter, I have been experimenting with that. If you paste this into the filter box (click the "..." button), it asks you for a match string, and then filters the list for triggers that have in their match text, somewhere, the match string:



It remembers your previous match string in a variable, so you only need to hit Alt+I next time around, and then <enter> to have that last item in the list.

Oh, that'll be handy as the list grows. Much thanks. :)

Since Wine won't let me reorder the titles through the GUI, is the order stored somewhere in a config or registry entry?

It is in the Registry, however if Wine doesn't support moving the labels manually, it might not support the changes if they are in the Registry either.

I'm not sure how it works on Dmpk2k's system, but for my system under Wine you can grab the labels and slide them to a new position, but they don't move when you unclick the mouse button.

I tried editing the "(alias|trigger) list Col \d Order" entries in the registry before firing MUSHclient up, but it made no different. Ah well, it's not to be.

> for my system under Wine you can grab the labels and slide them to a new position, but they don't move when you unclick the mouse button.

Same. They snap back to their original position.

Dragging the headings generates windows messages that Wine is probably not programmed to respond to, at this time.

It says a lot of good things about MUSHclient to know that I've filled out more reports wanting to get things fixed in wine for your client than I have for any game or office program I've used.

Does the LoadPlugin function also call on some Windows function Wine can't handle as well? I can't seem to load anything up no matter how I put the paths in. Full path, relative path, dos style, *nix style, whatever. It just can't find the plugins that way. Loading them up through the normal plugin window works fine though.

Make sure you are checking the return code. I tested LoadPlugin under my version of Wine and it worked OK.

Try this:


require "check"
check (LoadPlugin ("yourpathnamehere.xml"))


Some problem with LoadPlugin will now be reported with a readable error message.