Zugg Software :: View topic

Posted: Sun Oct 11, 2009 3:45 pm

I'm not sure exactly how i managed to do this, but i've been getting odd errors from trying to map, even using the find feature on the scrollback buffer.
After I try, typing at the command line will pop up an error, although i can type into editor window just fine.
After some looking around i found what seems to be the problem:

I cannot seem to close any of the extra copies of the map.
Anyone had troubles similar or know how to fix?
I'm bout ready to reinstall.

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

Probably a corrupted layout. First order of business is to close the session and then reopen while holding down the SHIFT key.

You may or may not have duplicate locations, so once you get the windows resituated you may want to open the package editor, use the Show Locations menu to make the locations visible (by default, they are hidden), and then delete any location object you find that you cannot account for. Assuming you are not maintaining different ones for different characters you play via this session (heh, further assuming that this sort of management is possible without screwing things up even more), unless there are duplicates there should only be one location.

Posted: Mon Oct 12, 2009 7:23 pm

That does temporarily fix the problem.

However upon using the find feature (success or fail) afterwards i still cant type on the command line without throwing up an error.
After closing the program and reopening the session, multiple map windows are open again, though only one is docked.

I only have the one location as I only have the one active connection in this session.

Posted: Mon Oct 12, 2009 10:48 pm

The "TMapFr.GetGrid" is a know bug in the current 3.10 version.

I'm not sure why you are getting multiple mapper windows though. I don't think that's related to the error. If you just open and then close your session does it create a new map window?

Make sure you only have a single Map Object in your settings.

Try to verify if it's just the #FIND command that is causing the duplicate. Also, are you remembering to click the Map Mode before using #FIND?

Posted: Mon Oct 12, 2009 11:46 pm

Just the one map object.
I'm not using the map #FIND but the find feature (CTRL + F) for the scrollback buffer.

And no, its not JUST the find feature, I seem to get multiple maps and this command line issue from anything giving me a system message box, including:
#HELP badhelpfilename
#PICK
#YESNO
and likely others as well

And yes, simply reopening the session alone will create an extra map as well, though not as many.

Posted: Tue Oct 13, 2009 5:08 pm

OK, if just reopening the session creates an extra map, then you definitely have a multiple location or something like that causing the extra map window to be created. I cannot reproduce this at all here, so it has to be something in your specific settings.

It might be time to export everything to XML and then create a new session and then import your XML scripts.

Posted: Tue Oct 13, 2009 7:17 pm

If i do have another, it must be well hidden

Is there a way to export the full package, or do i have to do each window/module separately?

Posted: Tue Oct 13, 2009 7:21 pm

Select the File/Export All menu option. That will export the entire package.

Posted: Tue Oct 13, 2009 8:52 pm

Additionally if you have numerous packages, you can click the "All" tab, click on first module, shift+click last, right mouse click export selection

Posted: Tue Oct 13, 2009 9:35 pm

Creating a new session did not resolve this issue.
In fact, I just tested and i get the error in the default session as well.
Back to a reinstall I guess.

Posted: Wed Oct 14, 2009 4:43 pm

You might want to try deleting any DEFAULT.PKG file that you might have in case it got corrupted.

Otherwise, if you get this error in a default session, then please post the step-by-step instructions for reproducing the problem. You should know by now that when beta testing you need to give me step-by-step details to reproduce a problem before I can fix it.

Posted: Wed Oct 14, 2009 5:56 pm

all i did was hit escape for the default
ctrl +f for the find window
enter a bogus word and let it search
as soon as it fails hit ok, and cancel
then try to type on the command line
error pops up

Since the default has no map i cant really tell if that aspect is happening or give a step by step for it.. however the issue is happening in other sessions as well, which is why I thought a reinstall was the best/only option left for me

Posted: Wed Oct 14, 2009 8:20 pm

Nope, that doesn't happen here. So it must be a DEFAULT.PKG or some other corrupted file in your CMUD directory. Definitely sounds like you need to backup and delete your CMUD Data files and then reinstall.

Or, first try deleting any DEFAULT.PKG in your CMUD Data Files directory (or the packages subdirectory) and also delete any CMUD.TBZ or CMUD.XLY file in your Data Files that might be loading.

Posted: Wed Oct 14, 2009 8:35 pm

An odd Note..
I had CMUDPRO running and went to delete the default package.. had no problem, but then i went into the regular CMUD directory to get its default package.. and it said it was in use.... I don't see why CMUDPRO would be using files from the CMUD directory instead of its own.

Posted: Wed Oct 14, 2009 9:29 pm

Both CMUD and CMUDPro use the files in the same "Data Directory". They share the same registry key for the data directory because all of the data files are compatible between the two versions. There is no way to make CMUD and CMUDPro use different data directories.