Zugg Software :: View topic - [2.06] Crash with hidden child window and automapper

Enchanter Joined: 09 Sep 2007 Posts: 605

1. Launch CMud
2. Close Sessions Window (ESC)
3. Open Package Editor (CTRL-G)
(C) Vijilante Wink

4. Create a new window, name it somehow and untick "Window is Visible" checkbox. Save and close the editor.
5. Click on the Map button on CMUD toolbar. This brings up the automapper window with default (empty) map.
6. In CMUD menu choose "Close session" or "Close all" item to get the error message:

Enchanter Joined: 09 Sep 2007 Posts: 605

Well, I believe that bug with hidden window and mapper is related to another crash I've got. Can't reproduce it in a new session; it seems to be package-dependent and even opening order dependent. So I gonna describe it here in hope that fixing the first bug will get this fixed too. If not - than I'll start a new thread for 2.07. I've found this bug by accident: first, I'm not use multisession at all, and second: CMUD still not run maximized by default and when I've missed the main menu, I click on CMUD window caption instead, causing it to move.

I have 2 sessions: my primary session and test session.
Primary session: main window + on top of it 5 tabbed child windows + docked to main window mapper window (right, top) and status window (right, bottom). Settings: Show containers:no, Show Caption:no
Test session: main window + invisible child window + empty mapper window (docked to the right of main). Settings: Show containers:no, Show Caption:yes

If I open first my primary session and then my test session, I'll have no tabs to switch between sessions, not any single tab to switch to any window of primary session. I need to use CMUD Window mune to switch windows. I see only 1 tab for main window of test session and automapper, showing the map for primary session. Normally, if open 2 or more sessions, you do get those session tabs. Strangely, if I open my Test session first and primary session after it, I'll get these tabs. I can't understand how is the order in which sessions are opened produces so different results.

The problem: at the point when there is no session tabs visible (although I have 2 or more sessions opened), if I gonna try drag CMUD window, it crashes immediately after window makes any movement. Here is the call stack.

Posted: Tue Oct 16, 2007 8:09 pm

I think part of the problem with that is that both sessions use the Mapper window, and currently the mapper window only works in a single session. So I think it gets confused about which session "owns" the single mapper window.

It's also possible that the XLY layout file for one or both sessions is messed up. Have you tried opening them but holding down the Shift key when you click the Open Offline to ensure that no XLY file is loaded?

When you open a second session, CMUD turns off the AutoSave option for the XLY layout. But if you ever some how force it to save the layout when multiple sessions are open (like using the #SAVE command), then the layout will contain all of the windows for both sessions. And when this XLY file is loaded in the future when all of those windows don't exist (like you open it first before the 2nd session is opened), then the docking system has trouble because the XLY file refers to windows that don't exist yet. I do some tricks to try and stop this from happening and causing trouble, but the docking system can be pretty finicky (and yet still works 100% better than most other systems I have tried).

Enchanter Joined: 09 Sep 2007 Posts: 605

Posted: Tue Oct 16, 2007 10:06 pm

Yeah, I think I just reproduced this myself. Looks like there is a problem when you change how windows are docked while the mapper is open. It saves the layout just fine, but then crashes when closing. So I'm working on that one. I'll also look at the AutoSave, although I think it's just disabling autosave internally and not actually changing the UI option (so that you can't accidentally turn if back on). In other words, I think it is supposed to just ignore your autosave setting when you open more than one session.

Posted: Tue Oct 16, 2007 10:16 pm

Wow, this was nasty. If you drag any child window and change it's docking position, then when the docking system recreates the mapper panel, the mapper gets assigned to this child window. So not only is the mapper assigned to the wrong window now (won't speedwalk properly...sends the mapper descriptions to the child window, etc) then also when you close CMUD, it tries to close the mapper twice (once for the main window, and once for the child window, which are both pointing to the same mapper window). This causes the crash. But as you can see, the real problems were much worse than the crash on exit and explains several other bugs that have been reported.