Is there a way to tell the mapper where to look for its database in cases where getMudletHomeDir() is having problems? One of our testers is on Ubuntu and seems to have a problem with Mudlet finding its home dir, so images won't load and the mapper won't work. For the images part, I just told him to...

I guess it would. What would be even better would be a button next to the command line, where the Emergency stop and other things are. That's how it used to be in ZMud, and I used it a lot there.

I would love to have an easy toggle for disabling/enabling the command separator - either a keyboard shortcut, or an easily accessible button. (I want it disabled when I'm coding, but enabled when I'm testing, and changing it in Settings every time is just too much hassle.)

The label is not part of the Mapper, it is a layout label that is drawn underneath the mapper (and is meant to be covered by it, so it is not something I would like to draw inside the mapper). I am using Geyser, but I tried with vanilla mudlet labels and the problem exists with those as well.

I saw your window management system. But in fact for my layout Geyser positioning works like a charm, or has so far. This is the first possible hurdle, and if necessary I will write a script to handle it. I sure don't feel like rewriting the whole damn GUI.

Yeah, I'm using Geyser. But when debugging the original problem, I tried everything, including vanilla labels with pixel size. It didn't make any difference. The dragging functionality just will not work wherever the mapper overlaps the label beneath.

It would play merry hell with window resizing. At the moment, the 100% width takes care of that, if I split it or compute a pixel width for it, I will have to redraw it every time the window is resized. That can be done, of course, but I would rather leave it as the last resort.

I partly solved the issue by splitting the immediate border into 4 labels that are drawn around the mapper. However I still have another label behind that's no easy to get rid of, because it runs along the top window border at 100% width. The rooms cannot be dragged further up than the bottom of thi...

It is definitely behind the mapper. It loads first, and I can click through it - I can select the room, but not drag it.

Edit: also, the label has a background image, so if it was in front of the mapper, I would not see it at all.

I wanted to put a label with a border image behind the mapper widget, but I noticed that when I do that, it is no longer possible to manually move rooms in the mapper (moving them by setting coordinates still works). When I remove the background label, everything starts working again. After further ...