macOS room dialog's save button


Jor'Mox
Posts: 1099
Joined: Wed Apr 03, 2013 2:19 am

Re: macOS room dialog's save button

Post by Jor'Mox » Tue May 22, 2018 10:17 am

So, I ran that version, and tried to change the door info for an exit in my map, and then changed it back, before closing the dialog box, and then quitting Mudlet. It generated the following output:

Host::Host() - restore map case 4 {QTimer::singleShot(0)} lambda.
TMap::restore( "" ) INFO: restoring map of Profile: "default_host" URL: ""
[LOADING PROFILE]: "/Users/zhiland/.config/mudlet/profiles/DSL MUD/current//20-05-2018#08-25-24.xml"
Host::Host() - restore map case 4 {QTimer::singleShot(0)} lambda.
TMap::restore( "" ) INFO: restoring map of Profile: "DSL MUD" URL: "dsl-mud.org"
"Mozilla/5.0 (Mudlet/3.9.0-testing-PR1672-46e1fb4)"
dlgMapper::dlgMapper(...) INFO constructor called, mpHost->getName(): "DSL MUD"
TConsole::createMapper() - restore map case 2.
TMap::restore( "" ) INFO: restoring map of Profile: "DSL MUD" URL: "dsl-mud.org"
"Mozilla/5.0 (Mudlet/3.9.0-testing-PR1672-46e1fb4)"
"Mozilla/5.0 (Mudlet/3.9.0-testing-PR1672-46e1fb4)"
"Mozilla/5.0 (Mudlet/3.9.0-testing-PR1672-46e1fb4)"
"Mozilla/5.0 (Mudlet/3.9.0-testing-PR1672-46e1fb4)"
"Mozilla/5.0 (Mudlet/3.9.0-testing-PR1672-46e1fb4)"
"Mozilla/5.0 (Mudlet/3.9.0-testing-PR1672-46e1fb4)"
"Mozilla/5.0 (Mudlet/3.9.0-testing-PR1672-46e1fb4)"
"Mozilla/5.0 (Mudlet/3.9.0-testing-PR1672-46e1fb4)"
"Mozilla/5.0 (Mudlet/3.9.0-testing-PR1672-46e1fb4)"
"Mozilla/5.0 (Mudlet/3.9.0-testing-PR1672-46e1fb4)"
"Mozilla/5.0 (Mudlet/3.9.0-testing-PR1672-46e1fb4)"
"Mozilla/5.0 (Mudlet/3.9.0-testing-PR1672-46e1fb4)"
"Mozilla/5.0 (Mudlet/3.9.0-testing-PR1672-46e1fb4)"
"Mozilla/5.0 (Mudlet/3.9.0-testing-PR1672-46e1fb4)"
"Mozilla/5.0 (Mudlet/3.9.0-testing-PR1672-46e1fb4)"
"Mozilla/5.0 (Mudlet/3.9.0-testing-PR1672-46e1fb4)"
"Mozilla/5.0 (Mudlet/3.9.0-testing-PR1672-46e1fb4)"
"Mozilla/5.0 (Mudlet/3.9.0-testing-PR1672-46e1fb4)"
"Mozilla/5.0 (Mudlet/3.9.0-testing-PR1672-46e1fb4)"
"Mozilla/5.0 (Mudlet/3.9.0-testing-PR1672-46e1fb4)"
dlgRoomExits::initExit() INFO - calling makeExitFromControls for original exit in: 3 direction code "northwest" direction.
dlgRoomExits::initExit() INFO - calling makeExitFromControls for original exit in: 1 direction code "north" direction.
dlgRoomExits::initExit() INFO - calling makeExitFromControls for original exit in: 2 direction code "northeast" direction.
dlgRoomExits::initExit() INFO - calling makeExitFromControls for original exit in: 9 direction code "up" direction.
dlgRoomExits::initExit() INFO - calling makeExitFromControls for original exit in: 5 direction code "west" direction.
dlgRoomExits::initExit() INFO - calling makeExitFromControls for original exit in: 4 direction code "east" direction.
dlgRoomExits::initExit() INFO - calling makeExitFromControls for original exit in: 10 direction code "down" direction.
dlgRoomExits::initExit() INFO - calling makeExitFromControls for original exit in: 8 direction code "southwest" direction.
dlgRoomExits::initExit() INFO - calling makeExitFromControls for original exit in: 6 direction code "south" direction.
dlgRoomExits::initExit() INFO - calling makeExitFromControls for original exit in: 7 direction code "southeast" direction.
dlgRoomExits::initExit() INFO - calling makeExitFromControls for original exit in: 11 direction code "in" direction.
dlgRoomExits::initExit() INFO - calling makeExitFromControls for original exit in: 12 direction code "out" direction.
dlgRoomExits::slot_checkModified() INFO - calling makeExitFromControls for current exit in: 3 code direction.
dlgRoomExits::slot_checkModified() INFO - calling makeExitFromControls for current exit in: 1 code direction.
dlgRoomExits::slot_checkModified() INFO - calling makeExitFromControls for current exit in: 2 code direction.
dlgRoomExits::slot_checkModified() INFO - calling makeExitFromControls for current exit in: 9 code direction.
dlgRoomExits::slot_checkModified() INFO - calling makeExitFromControls for current exit in: 5 code direction.
dlgRoomExits::slot_checkModified() INFO - calling makeExitFromControls for current exit in: 4 code direction.
dlgRoomExits::slot_checkModified() INFO - result, isModified: true
dlgRoomExits::slot_checkModified() INFO - calling makeExitFromControls for current exit in: 3 code direction.
dlgRoomExits::slot_checkModified() INFO - calling makeExitFromControls for current exit in: 1 code direction.
dlgRoomExits::slot_checkModified() INFO - calling makeExitFromControls for current exit in: 2 code direction.
dlgRoomExits::slot_checkModified() INFO - calling makeExitFromControls for current exit in: 9 code direction.
dlgRoomExits::slot_checkModified() INFO - calling makeExitFromControls for current exit in: 5 code direction.
dlgRoomExits::slot_checkModified() INFO - calling makeExitFromControls for current exit in: 4 code direction.
dlgRoomExits::slot_checkModified() INFO - calling makeExitFromControls for current exit in: 10 code direction.
dlgRoomExits::slot_checkModified() INFO - calling makeExitFromControls for current exit in: 8 code direction.
dlgRoomExits::slot_checkModified() INFO - calling makeExitFromControls for current exit in: 6 code direction.
dlgRoomExits::slot_checkModified() INFO - calling makeExitFromControls for current exit in: 7 code direction.
dlgRoomExits::slot_checkModified() INFO - calling makeExitFromControls for current exit in: 11 code direction.
dlgRoomExits::slot_checkModified() INFO - calling makeExitFromControls for current exit in: 12 code direction.
dlgRoomExits::slot_checkModified() INFO - result, isModified: false
mudlet::saveWindowLayout() - Already-Saved: false
cTelnet::~cTelnet() Instance being destroyed before it could display some messages,
messages are:
------------
[ OK ] - Lua module rex_pcre loaded.
------------
[ OK ] - Lua module zip loaded.
------------
[ OK ] - Lua module lfs loaded.
------------
[ OK ] - Lua module sqlite3 loaded.
------------
[ OK ] - Lua module utf8 loaded.
------------
[ OK ] - Lua code formatter loaded.
------------
[ INFO ] - Auditing of a loaded/imported/downloaded map starting...
------------
[ OK ] - Auditing of map completed (0.00s). Enjoy your game...
------------
[ OK ] - Map loaded successfully (0s).
------------

User avatar
SlySven
Posts: 919
Joined: Mon Mar 04, 2013 3:40 pm
Location: Deepest Wiltshire, UK
Discord: SlySven#2703

Re: macOS room dialog's save button

Post by SlySven » Tue May 22, 2018 4:33 pm

*biting his fingernails* - yeah but did the Save button visibly enable itself when it said: "dlgRoomExits::slot_checkModified() INFO - result, isModified: true" and disable itself when it was "dlgRoomExits::slot_checkModified() INFO - result, isModified: false" ???

Jor'Mox
Posts: 1099
Joined: Wed Apr 03, 2013 2:19 am

Re: macOS room dialog's save button

Post by Jor'Mox » Tue May 22, 2018 4:40 pm

No, the Save button remained grayed out the entire time. Granted, it became actually enabled when there was a change to save (and disabled when I undid that change), but the visual effect didn't occur.

User avatar
SlySven
Posts: 919
Joined: Mon Mar 04, 2013 3:40 pm
Location: Deepest Wiltshire, UK
Discord: SlySven#2703

Re: macOS room dialog's save button

Post by SlySven » Tue May 22, 2018 4:58 pm

Aaaaaaarrrrrgggh!

It seems we are not the only ones with this problem: QTBUG-68067.

User avatar
SlySven
Posts: 919
Joined: Mon Mar 04, 2013 3:40 pm
Location: Deepest Wiltshire, UK
Discord: SlySven#2703

Re: macOS room dialog's save button

Post by SlySven » Tue May 22, 2018 6:25 pm


Jor'Mox
Posts: 1099
Joined: Wed Apr 03, 2013 2:19 am

Re: macOS room dialog's save button

Post by Jor'Mox » Tue May 22, 2018 6:30 pm

Yes. The save button properly changes appearance in this version.

If any of that magic could be applied to get the window size to be saved between sessions, that would be awesome, as that is honestly far more irritating to me personally.

User avatar
SlySven
Posts: 919
Joined: Mon Mar 04, 2013 3:40 pm
Location: Deepest Wiltshire, UK
Discord: SlySven#2703

Re: macOS room dialog's save button

Post by SlySven » Tue May 22, 2018 6:56 pm

Unfortunately I suspect it is a completely different issue which just happens to have occurred at roughly the same time Anyhow I'd better clean-out the test code and polish up a proper fix for this one.

Post Reply

Who is online

Users browsing this forum: No registered users and 7 guests