Zugg Software :: View topic - [310B] Problems with the mapper adding a map to a new package.

Posted: Thu Aug 20, 2009 7:20 am

If have encountered the following problems trying to add an SQlite3-based map file to a new package:

The map loads but attempting to select a room as the current location (by using the menu option) fails.

Assuming that the problem is related to the lack of Location object. I attempt to create a location object for the map. Creating the object is no problem, the problem is that the object is not added to the settings. This, of course, prevents me from tracking the object and getting a room to be the current one.

When I click on MAP on the main session taskbar, since there is no mapper entry in the settings, an "untitled" map is added to the settings (IMHO this should be changed, if there is no map I should have the option of loading an existing map, then if I don't, a default map can be added). Then when I use the Open option in the mapper menu and fetch my map, another entry is added to the settings. So now I have two map entries in my package. This hampers the creation of Location objects, because CMUD insists on adding the objects to the "untitled" map, rather than the map that I loaded. Deleting the unwanted map entry helps, but then the problem mentioned above takes over. I must note here, that the location object drop down list at the bottom of the map display does not acquire the added object names (in fact, it remains black), so tracking by selecting from this list is no available.

Lastly, when I save the package, close CMUD, re-open CMUD, and re-load the package, I find that the map entry I created is not saved. So I think, that a map without location objects is not considered a map and not added to the package, though that's my opinion. I really have no clue as to what the problem is. Note that manually adding the XML for the map entry to the settings, saving the settings, and reloading them as described above, does keep the added entry, but won't automatically load the map even though the box is checked. In fact, this manually added entry to the settings is useless.

This was my first attempt to add a map to a new package. I had always worked with the converted map. The conversion obviously took care of creating a default Location object and to begin tracking it. However, converting a map is not an option since the only jet map I have is way out of date.

Posted: Thu Aug 20, 2009 4:23 pm

Posted: Fri Aug 21, 2009 12:25 am

This is the point. This is not a shared package, this is a pristine package intended to be the default session package. When it loads the first time there is no map. When I click on MAP, a default map entry is created (which is normal), then when I select the map I want from the Open mapper menu, my map loads with no Location object. Attempts to create a Location object for the map fails. That is why I posted. When I enter #LOC on the command line it says "no locations", before or after I attempt to create the object. Since there is no Location object, there is nothing to track, and I believe this is the reason selecting "current location" from the context menu does nothing. I've tried creating the object both via the menu and by script (command line). When I use the View/Locations menu, and attempt to create the object "succeeds", but no object appears either by executing a #LOC or by viewing the drop-down menu at the bottom of the map display. I never had ran into this before because the package I am currently using contains the map that was converted from jet. So the conversion routine took care of setting it up and I assumed it also created the Location object. This is happening because I am adding an already-converted map. Of course, it could be the case that I am doing it all wrong and that is why it doesn't work.

EDIT: IMHO, I think that selecting a room as the current location should create a Location object if none exists. There is no functional difference between selecting a "first" room and creating a "first" Location object for the map. Even if what I described above is not an error but a mishandled procedure on my part, this suggestion has merit because its intuitive nature.

Wizard Joined: 22 Mar 2007 Posts: 2320

I just tried to follow what you did. I created a new session. I clicked Map to create a new map. This also created a location object for me. In the mapper window, I clicked Open, and opened another existing map. I deleted the new, empty map. When I type #Loc, I see that my location object is connected to the map that remains. Setting a location in the mapper window works fine. I don't see a problem here. What exactly did you do differently?

Posted: Fri Aug 21, 2009 2:22 am

I didn't do that. What I did is I created a package and gave it the same name as my current session package (stored in a different location, of course). The idea behind this new package was to get a clean session package without all the baggage that it has been dragging since CMUD 1. I then renamed the old package and move the new package in, I started the session offline and the package loaded just fine. What didn't work (and still hasn't worked) for me was adding the map to the session. That is when the problems described above happen. I tried your procedure and it worked for me, also. However my procedure and yours are slightly different though one would think that they were equivalent.

Wizard Joined: 22 Mar 2007 Posts: 2320

One reason that would be different is because the layout file is still the old one, and thinks there is a mapper window. Try getting rid of the .xly file.

Posted: Fri Aug 21, 2009 4:02 pm

Anaristos, creating packages and moving them around and changing file names is not a good way to do things in CMUD. As Rahab mentioned, some files, such as the layout file, are tied to unique key values stored in your package for your session windows.

The proper way to create a "clean" package file is to click the Edit Session, then Files/Packages and change the name of the primary settings file. Then load offline and CMUD will create a new package and layout file with the new name. Or, you can delete/rename the existing *.pkg file, but you also need to delete/rename the associated *.xly and *.tbz window and toolbar layout files.

Posted: Sat Aug 22, 2009 2:18 am

I will use the procedure you indicated. Thank you.

I still think that if a map has no location object clicking on a room should create one since the action indicates that the user wants that to be the current location. Perhaps this is something that can be added later. Also, perhaps, the location management dialog box could be either move to, or duplicated in, the mapper menu. It would make it a lot easier to use since this placement is more intuitive.