Zugg Software :: View topic

SubAdmin Joined: 18 Nov 2001 Posts: 5182

I can't really be sure whether this one is new or matches some of the old crash on close issues.

Procedure
1. Launch CMud
2. Close Sessions Window (ESC)
3. Open Package Editor (CTRL-G)
4. Select New|Window
5. Enter name for the window and click save changes
6. Change window to floating in Package Editor and click save changes
7. Change window to tabbed in Package Editor and click save changes
8. Close CMud by clicking X

Posted: Sun Oct 14, 2007 2:24 pm

Confirmed.

SubAdmin Joined: 18 Nov 2001 Posts: 5182

This one still occurs in 2.07

Posted: Mon Oct 22, 2007 7:31 pm

Yep, still on the bug list. A lot of your reported bugs doing weird things in the package editor didn't get fixed in 2.07 since they mainly involved procedures that are not encountered commonly in normal usage. So they didn't have as high of priority as some other bugs.

SubAdmin Joined: 18 Nov 2001 Posts: 5182

What is truly funny about that statement is that I *never*, with any version of CMud, have been able to make a successful import of my settings. All of these procedure I find to replicate crashes or other bugs are from tracking down something that I noticed going wrong while attempting to import and organize the settings from my .mud files. I haven't been able to test every version, I did make a pretty close attempt though.

Posted: Mon Oct 22, 2007 10:33 pm

OK, even with v2.07? I've tested the *.MUD files that you posted to the Guru forum and they both import just fine for me here in v2.07. So if you have some other *.MUD files that are not importing, please post them so I can test them.

SubAdmin Joined: 18 Nov 2001 Posts: 5182

It is not so much the import/conversion that fails. It is all the the things I do organizing those settings that starts finding stuff. For example my zMud mapping script is half in the main window and half in a childow. Among the first things I do after importing that child window's .mud is add some modules in it so I can bring the 2 halves together into a single package. Then I start moving the stuff from the main package into the second package. That is what leads to most of these bugs that I find and keeps leaving me frustrated. That particular move is actually what lead to me finding the problem with alarms in disabled classes. That same move is the one that caused a totally horked package in 1 shot with 2.07, however it seems that was 1 in a million shot.

Just a few months ago I would have responded to seeing that horked package by uninstalling CMud and walking away from computer saying, "I can't use this #$%$^!" My home situation and circumstance in my life took far too much of my thoughts to track down such bugs. I was definitely upset enough with those other issues that I only reported at best a few bugs each version; and if I bumped into a bug I had already reported in a previous version first I just stopped and uninstalled and didn't report anything.

I am sure it is frustrating for you to read my statement above (both the recent paragraph and my previous post), and if it is any consolation I think I just had a good import made since I knew just about thing I should not do in the entire process. I will give you reports on other bugs when I am a bit less snippy.

Yes, I agree the bug procedure in this thread is defnitely outside normal usage. If I remember right I was trying to adjust my layout at the end of what seemed a good import in 2.06 and bumped into a crash. Next time I load up I find that in my rush that have a good directory of everything I could backup, I just lost a whole bunch of things. Of course that leads me to hunt the bug down with a vengenance. I don't stop hunting that until I find a procedure that replicates it, no matter how ludicrous the procedure is. I bumped into the bug during normal usage, and someone else will to.

Posted: Tue Oct 23, 2007 1:59 am

Posted: Tue Oct 23, 2007 2:15 am

Btw, I should also add that the bugs dealing with the Package Editor are some of the most difficult and frustrating ones for me to work on. The package editor is *so* complex that it's really easy for a bug "fix" to have unintended side effects. So fixing a new bug can often cause some old bug to re-emerge again. And it's nearly impossible to do automated testing on this particular module (unlike the parser, for example).

For example, the latest bug where it doesn't update the tree after your move something (either with MoveTo or with drag/drop) is new. I wasn't seeing that in past versions, but I reproduced it in the 2.07 version. I have no idea why it started doing that. But hopefully by pounding on these bugs I can slowly improve it and make the code a bit more stable. It's one of the reasons I'm so hesitant to replace the TreeView since it would mean starting over on bug fixing. So even though the current TreeView is a pain to work with, at least I've built up a fairly extensive set of fixes for it.

Anyway, I just fixed the problem with the tree update and I can see that it would be really frustrating to move settings around with that bug. So I'll try to get 2.08 out later tonight with some of these serious bug fixes.

Posted: Tue Oct 23, 2007 2:24 am

I've also fixed 2.08 so that it won't let you delete the package that contains the currently active session window (the Untitled session in your examples). This should prevent some crashes and corrupted settings.

But I'm also kind of curious as to why you were deleting the Untitled package in the first place...was it just to reproduce a crash, or is there a real reason that you need to do this to convert your existing settings?

SubAdmin Joined: 18 Nov 2001 Posts: 5182

Sorry I wasn't clear on what X to hit with the bug report you mention. It is in another topic by the way, and it will confuse both of us for me to post about it here. I will post something there, just before I zip up my good looking packages and layout and start fresh with 2.08.