Mudlet features and API requests

[Jor'Mox]

Unfortunately, it has been a recurring issue with Mudlet on the Mac, with multiple different versions doing the same thing, before some other version comes out that fixes it. It makes me wonder if it is the same problem being pulled back into the code repeatedly, as otherwise there would have to be several different ways that the exact same problem could be made to happen, and it would be weird for there to be so many different pieces of code that could dictate initial screen size.

[Vadi]

Nothing related to screen size has been changed in a very long while that I remember... SlySven?

We should continue the discussion on that ticket.

[SlySven]

There is code that I haven't grokked to save and restore the placement of (I think) things that are independent of the main application window (again, I think): floating toolbars, "user" windows (the floating, dockable one) as well as the main window. IIUIC that ultimately comes down to the Window Manager - something outside of the Mudlet application - listening to and responding to the placement requests that Mudlet makes {but that may be an X11 - i.e. a Linux/FreeBSD thing and I do not know if macOs/Windows does exactly the same thing].

If we gained a developer who has a real Mac to work on it may improve our chances of solving issues that specifically manifest there; I just do not know yet of any, err, intrepid coders in C++ who use that platform and use Mudlet and want to put themselves forward, they would, I feel, be warming welcomed into the fold.

[Nanocore]

I have the qualifications that you specify except Im a mudlet newbie. The only other problem is I may not have that much time to work on it. Spurts here and there, but am motivated at the moment having just started with MUDs.

[Jor'Mox]

Just wanted to report two issues that have popped into my awareness recently. The first is that if you uninstall a module, temp aliases are placed in the list of aliases in the GUI. As far as I know, this doesn't affect performance, but can cause some confusion/irritation for users until they restart Mudlet, at which point they disappear. The second is that in the mapper, if you edit a room's exits via the menu, and change only the door status for an exit, the Save button does not appear to become activated. You can never the less actually still click the button, but visually it looks as if it is disabled. Again, this is more of an irritant than anything, but I can see how it might confuse some people.

[Zaphob]

Each size is a multiple of 8px x 1,2,3 or 4 (so that is 8x8, 16,x16, 24x24 or 32x32) - what is probably not helping is that sizes 3 and 4 also include texts and some of those are a bit long IMHO - I plan to change "Package Manager" / "Module Manage" to just "Packages" / "Modules" - which should help - and then let me stuff in "Close" and/or "Mod. Exporter".

Maybe make text display optional? We always have mouse-over.

[Vadi]

The entire menu is optional already, you can replace it with a menu bar if you'd like.

[Vadi]

@Jor'Mox: confirmed the first issue https://github.com/Mudlet/Mudlet/issues/1645

For the door issue, could you re-rest with 3.9?

[Zaphob]

The entire menu is optional already, you can replace it with a menu bar if you'd like.

I know this, but the suggestion was to have a bigger icon size, but not with as much space as the text needs. So a solution may be to toggle icon size and text display independent of each other.

[Vadi]

I think the renaming will be enough. Very few people toggle between the menubar and toolbar already, adding even more super-specialised options to one doesn't seem worthwhile right now.