So, I saw you mention something about pushing out another preview in 3 weeks or so. I know that you're focusing on bug-fixes and the like, but I'm fairly certain getMousePosition() couldn't create any bugs(since it doesn't really touch anything outside of the function itself), adding it is a matter ...

@SlySven I only added the getMousePosition function via source, the rest was a script in mudlet that drew a label and toggled the image-moving timer on click. No clue where Map Labels even are in the code? I've personally never really used the mapper much, generally staying away from images in my GU...

So, since ultimately my point was making my labels dragable in some manner, I decided to try and make the change that I thought would make this possible with the least amount of messing around in the code. About 6 lines of code later, I have a working getMousePosition function added to Mudlet that r...

Well, at this point it's more about the small things that would get Userwindows to a point where they were functional enough that I think people would actually use them. There is a little bit of simple functionality needed that would get it to the level that I would use it for at least a few things:...

Due to someone asking what options they had for dragable labels and the like, I started looking around at the code for userwindows to see how much work it would take to get support for moving and resizing userwindows added. Seems like a surprisingly small amount of work, so I'll probably poke around...

I've seen this same thing occur a few times as well recently. Since I was running off a version I'd compiled with a handful of changes, I was worried it was something I had done. Glad to see that's not the case I guess? I'm almost positive it is related to searching scripts, as it hasn't happened in...

Coming from Imperian, we have many players that are sight-impaired. Hell, our single greatest combatant plays using nothing but a screen reader for feedback. He uses MUSH however, because he is partial to Python, and partly because (from what I understand) Mudlet isn't as friendly on screenreaders a...

I feel like I remember seeing somewhere the reasoning behind the scrollTo function not being exposed to scripts. Am I mistaken? If nobody knows, I can just add it in a custom compiled Mudlet and play around to see if anything breaks.

Gotcha. Another thing I'm unsure about. I see there's an array of booleans associated with each Y line in the buffer, called "dirty". It is being defined by TBuffer at TBuffer.h#L135 , and is written to in both TBuffer and TTextEdit, but I don't see any place that it is being read, rather ...

Just gonna consolidate any questions I have while messing with Mudlet's code here, so I'm not starting a new thread every time I try something new. I see the QPoint mP_aussen being defined in the code in TTextEdit.h and TTextEdit.cpp. I don't see it ever being referenced though. Is it just a useless...