Zugg Software :: View topic

Posted: Sat Jun 27, 2009 11:10 pm

For some reason the location object becomes "lost" and has to be re-acquired by clicking on the mapper location object list. When the location object drop-down menu opens, a long list of blank (no-name) objects appear, as well as "objects" with names corresponding to secondary windows. When the object is "lost" a blank name appears as the current object.

EDIT: Using the VIEW|Locations to delete these "objects" does not work. It goes through the delete procedure (i.e. it asks if you really want to delete it) but the object remains. Each object name is black and the object room number is 0. There are over 20 of these items.

Posted: Sun Jun 28, 2009 12:53 am

That sounds similar to a problem I had, I was getting secondary location objects that were named after secondary windows, If I deleted them and restarted cmud i'ld get them back. The problem was a corrupted layout file, delete the secondary location objects, and use shift to reset the layout file. As for the location getting lost, i can't help you any there.

Posted: Sun Jun 28, 2009 10:23 pm

Since the location objects are not kept in the map database but are kept in the package file, I assume this is a file corruption problem. The fact that the "objects" can't be deleted strengthen this belief. However, the mapper finds them so once in a while it chooses one of them as the current location object as the one to be tracked which causes the tracking problems. I don't know what the choosing mechanism is so I can't figure out what the actual bug is.

Posted: Mon Jun 29, 2009 6:32 pm

As you mentioned, it sounds like the location objects in your package have gotten messed up and are "partially deleted" somehow. Try exporting your package to XML and then edit the XML in something like NotePad to remove any of the extra location objects. Then import back into CMUD.

Or, you can try going into the Settings Editor, and select View/Show/Locations to display the location objects and then see if you can delete them from that screen.

I just tested this in a new session and didn't find any problem. I created a couple of location objects using the #LOC command. Then I went to View/Locations and deleted one. Then I did #LOC and it wasn't displayed anymore. I exited and restarted CMUD to load my session and the location I deleted still wasn't there. So it seems to delete properly in a new session, which confirms some sort of corruption in your current location objects, possibly caused by a prior beta version.

Posted: Tue Jun 30, 2009 3:22 am

Deleting them in the Settings Editor worked fine. I must point out, though, that your test may not reveal the problem because the location objects were not created by any explicit means. They just appeared on their own. They must have been valid location objects because the mapper chose them at random and set them as the current object, which is how I found out that there was a problem.

Posted: Tue Jun 30, 2009 4:57 pm

If you open the mapper for a session window that doesn't have any location object, then CMUD will create a default location object. I'll look at the code that creates these default objects to make sure they are being created correctly.

Posted: Tue Jun 30, 2009 11:54 pm

I think you will be interested to know that there were 429 of this no-name objects created (that's the number I deleted).

Posted: Wed Jul 01, 2009 4:45 pm

Wow! Let me know if they start reappearing with the 3.08 version. My guess is that they were related to bugs in older beta versions, but let me know.