Zugg Software :: View topic - [2.23] PE shows wrong settings for selected tab

Wizard Joined: 25 Mar 2003 Posts: 1113 Location: USA

I'm not sure exactly what I do to make it get out of sync, but after rebuilding my two dozen packages fresh in 2.23 and reloading my session, I sometimes open the PE and see that the "LusterniaTest" tab is the active tab and the frames below are showing the settings for some other package. It happens every time I run CMUD, load my session, and open the PE, but only seems to happen once and after I sync it up by clicking around a bit, it's fine.

Posted: Mon May 05, 2008 5:03 pm

It should show the settings for whatever window has the current focus when you first open the package editor. I know you have a rather complex setup, but I'll need some sort of procedure to reproduce this one since I can't get it to fail here.

Oh, and the settings editor *does* save the "last selected" setting id for each tab in the package editor, so maybe it is trying to display a setting that no longer exists (because you recreated the package?). The method that you are using to recreate packages is probably driving your ID field values larger and larger, so maybe it's referring to a previous setting ID value when it saves the tab views.

Wizard Joined: 25 Mar 2003 Posts: 1113 Location: USA

Not too sure about re-creating it from scratch, but my setup isn't as complicated when this happens as it is when I'm fully loaded up. Smile

Just now, though, I opened my LusterniaTest session offline (without any packages or settings other than the LusterniaTest window) and opened my TreantCore.pkg in the PE. This is what I ended up with in the display:

The Treant Core module uses an onLoad event handler to create settings in the Treant Persistent module, which is created in the session's main package. The package I opened was created previously and not a new script import or anything.

Posted: Mon May 05, 2008 7:15 pm

Hmm, maybe CMUD is keeping the module created in onLoad as the current default module? If you click on your main output window first and then open the Package Editor, does it display the correct setting then? If you can show me the onLoad script that you are using, then I might be able to reproduce this.

Wizard Joined: 25 Mar 2003 Posts: 1113 Location: USA

I re-created it in a simpler way, but then it also crashed CMUD with a memory access violation. Hmmm.

1. ESC to get to default session.
2. Open PE.
3. File ->New Package -> named Test
4. In the Test package, create a new onLoad event.
5. In the onLoad event, put the code:

Posted: Wed May 07, 2008 10:51 pm

Well, this bug was almost the death of me. This took me three hours to track down today. The crash was different from the actual problem with onLoad not maintaining the current default context. The crash was related to removing a package after viewing something from that package in the editor (the onLoad event). The editor was caching a reference to the previous setting record (which is no longer valid after removing the package). And it turns out the Scintilla editor component was sending a background message to refresh itself, which was causing it to syntax check the script of the cached onLoad event.

Even after I fixed this it was still crashing until I found that it was also saving a pointer to the "preferences" of the previous script object, so that the parser could fetch stuff like the Var Character (special characters) to do the parsing. Each module has it's own preferences, so it was pointing to the preferences of the "test" package's main module that was just removed (and no longer a valid pointer).

Man, sometimes I really hate all of this caching. Seems like caching for performance causes the most bugs.

Anyway, I think both problems are solved in v2.24. Hopefully I didn't create any side effect bugs.

Wizard Joined: 25 Mar 2003 Posts: 1113 Location: USA

Hate to say it, but this still happens. I started over completely after deleting everything from 2.23. Created my core module, then the GUI module, then the stance module. After importing the last script, I re-opened the PE and saw that the Lusternia tab was selected, but the core module settings were shown.

Posted: Thu May 08, 2008 4:15 pm

As long as it's not actually crashing, then I'm not too worried. But I'll need another procedure for this since the procedure posted above works fine for me now.

Wizard Joined: 25 Mar 2003 Posts: 1113 Location: USA

I tried the procedure above, and that part works now because of the "switch module when switching package tab" change you made. However, if I add one or two more steps - close the PE and open it again - then it appears incorrectly again.