Another thing I remembered is that our consoles aren't HiDPI aware. On
macOS no option is needed to make Qt scale properly, but you'll see that
the main console is not crisp:
http://cl.ly/image/3a3B3t0Y3O1t
http://cl.ly/image/320v3M2J1H2h
So the above solution will only get us halfway there I
Public bug reported:
If the server sends a GMCP event with just the name and no payload,
json_to_value is given "" as data and it errors out.
It worked in 2.1 previously, broken in 3.0. First reported at
http://forums.mudlet.org/viewtopic.php?f=5=4610=70#p22035.
This in particular breaks
A fix would be just to check that string_data.size() isn't 0 in
https://github.com/Mudlet/Mudlet/blob/development/src/TLuaInterpreter.cpp#L12340
I imagine.
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
Still an issue in latest release_30.
** Changed in: mudlet
Status: New => Confirmed
** Description changed:
Compiling the "^mmdefs(?: (\w+)?$" pattern for an alias gave a blank
error message, instead of saying that there is an unbalanced
paranthesis.
+
+ Same for (? ).
+
+ It can
** Description changed:
- We should add xterm256 support for maching triggers with.
+ We should add xterm256 support for matching triggers with.
** Description changed:
- We should add xterm256 support for matching triggers with.
+ We should add xterm256 support for maching triggers with. Has
Public bug reported:
Passing in 13 as a dirType causes a "setExitStub: Need a dir number as
2nd argument" error. The logic should instead follow the current Lua
error message guidelines for reporting what the value is + say
"setExitStub: dirType must be between 1 and 10".
** Affects: mudlet
I just tried 28fda4d and yes, i have still the issue.
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1660082
Title:
Error on script registered on GMCP event
Status in Mudlet:
New
Bug
I'd imaging that could get very spammy with, e.g. "sysWindowResizeEvent"
events - if we were to implement reporting of "system" events I'd make
it a (globally, application wide) applicable check-box on the "special
option" but leave it disabled by default...
--
You received this bug notification
Sure thing. Will test tonight or tomorrow night.
I've since migrated to a Mac as my primary dev box so I'll have to get my
environment set up again for Windows builds.
-Colin
On Mar 5, 2017 4:00 PM, "Vadim Peretokin" wrote:
> Colin, you can add the ::setAttribute call to
Colin, you can add the ::setAttribute call to
https://github.com/Mudlet/Mudlet/blob/release_30/src/main.cpp#L113 -
between line 112 and 113 (after the else and before the #ifdef). Let me
know how you go - I haven't got a HiDPI screen to test with myself.
--
You received this bug notification
** Changed in: mudlet
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1419179
Title:
Opening mapper on OSX causes toolbar graphics corruption
Status in
Public bug reported:
Mudlet raised-events are not shown in debug nor main window - something
to think about, they should appear at least somewhere...
** Affects: mudlet
Importance: Wishlist
Status: New
--
You received this bug notification because you are a member of Mudlet
Sorry, we got distracted by the missing dictionary. Are you still having
the issue?
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1660082
Title:
Error on script registered on GMCP event
Status
let me know if want me to test it. thanks
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1374684
Title:
Crash on using the search box
Status in Mudlet:
New
Bug description:
See
14 matches
Mail list logo