Zugg Software :: View topic

Apprentice Joined: 03 Feb 2007 Posts: 170

When I create a new session and try to connect to it I get an error that pops up and tells me "There must be at least one field."

Posted: Fri Jun 06, 2008 5:44 am

Yeah. I actually saw this once, too. The steps that led to mine were:

1. Open up a blank session.
2. Import XML scripts
3. Open up Mapper and load a map
4. Close session window
5. Attempt to open up main session

At least, that's how I got it to show up.

Charneus

Novice Joined: 15 Aug 2007 Posts: 39

Second possibility to reach it:

- Go in Package editor
- Open a package that has also a Main window
- Close the first Main window

-> Fault appears.

I did the following to repair it:

In the Menu, chose Window, then the name of the first Main Window.

Posted: Fri Jun 06, 2008 5:37 pm

I am still unable to reproduce this new error. If you are importing something, then I'll need to see exactly what you are importing. I took a look at the crash dumps related to this error and it seemed to indicate that people were running live on the MUD with triggers firing when they did the XML import, so that might matter too.

I tried opening my own package with a window and couldn't get it to fail either, but you need to tell me *exactly* what you are doing and more exactly how you are "closing the first main window", etc. I need to know exactly what you click on or what keys you are pressing. There are lots of ways to do the same things in CMUD and it might depend on exactly which method you are using to close a window.

Beginner Joined: 13 May 2008 Posts: 25

I have received this error about 3 or 4 times, once utilizing the package editor and another time when I quit the mud I was playing, went to File->Close All, double clicked another session, and then it occurred. When I find a way to reproduce it I will post it in this or a new topic.

Beginner Joined: 13 May 2008 Posts: 25

Alright Zugg I found a way to reproduce this bug in my case. Here is the procedure, tested with various sessions. Start CMUD, double click a session to open online. Open the package editor and then close the package editor. Type quit (or whatever the command may be to disconnect from the mud.) Press work offline in the new dialog box that opens. Go to File->Close All to close the windows and go back to the sessions screen. When I double click a new session I get that error. Hopefully it reproduces for you since it does this with all my sessions.

*EDIT* Sorry about the double post, should we just edit our previous post instead? Like I said I am new to posting bugs here and just want to make sure I get these out here for you to solve as quick as possible.

Posted: Fri Jun 06, 2008 7:16 pm

Seems like the common denominator here is Closing Windows. Might be worth looking into.

Charneus

Posted: Sat Jun 07, 2008 1:33 am

OK, here is another way to get the error:
I copied some xml from one of the posts to test. I created a blank trigger setting, clicked on xml and pasted the xml into the box. When I tried to switch from xml to script, CMUD went into a (slow) loop posting the error message about at least one field being required.

EDIT: After re-starting CMUD, I went to the settings Editor and found that the pasted setting was there. This means that pasting into the xml box is not the problem in itself.

Apprentice Joined: 03 Feb 2007 Posts: 170

Nope, definitely not XML related, I've had it do it on sessions with no classes, triggers, aliases etc. nada, It seems to require restarting the program to solve each time.

Posted: Sat Jun 07, 2008 6:13 pm

With all due respect, Fizban, just because it didn't happen to you doesn't mean that it doesn't happen the way I described. I am not making any claims that XML is in any way involved. I am making the claim that when I pasted text into the XML box the error took place.

EDIT: the trigger code I pasted into the XML box is here. Give it a try. It is reproducible at will.

Apprentice Joined: 03 Feb 2007 Posts: 170

Oh, I wasn't meaning to say it didn't happen under those circumstances. I simply meant it definitely can occur without ding anything relating to XML.

Wanderer Joined: 28 Jan 2006 Posts: 60 Location: Scotland

For me I can reproduce this error by:

Since I can not get through my proxy to send the error report I include it here:

Enchanter Joined: 09 Sep 2007 Posts: 605

Ok, this bug today have crashed my primary session. While I fill-up the crash dump with my comments after, I've got an idea on how to recreate it.

The following sequence was tested in a test package and in the untitled session.

1) Start CMUD, hit Esc.
2) Enter at cmd line:

Posted: Mon Jun 09, 2008 5:57 pm

OK, I'm getting this error all of the time now too when trying to paste XML and when opening various sessions. I have no idea what is causing it, but at least now I can reproduce it to figure out what I changed to cause this. Definitely a serious problem, so you'll see v2.27 soon this week.

Posted: Mon Jun 09, 2008 10:06 pm

OK, found the bug and have it fixed for v2.27. I still have to work on some of the MXP color bugs with the new URL style, but it shouldn't be a problem getting 2.27 released later this week.

Posted: Thu Jun 12, 2008 12:02 am

Just to make a record of it, there is another way I've found to get the error. I attempted to cut/paste a setting from a module to a class under the session window. When I did the paste I first got an error saying that there was no valid XML data in the Clipboard, this was followed by the one-field error. Also, when I hit ESC the Settings Editor closed. When I reopened it, I got an empty package back (not even a root!).
Reloading the application showed that the package was still there.

EDIT: I found that the first setting for the session window (lexically speakng) into which I attempted to do the paste, is now blank. So the paste did some clobbering.

Posted: Thu Jun 12, 2008 12:12 am

Yep, actually Anaristos, that is the exact method I used myself to reproduce this bug. But the bug was actually at a very low level part of the code, so there were a large number of ways to trigger it. As evidenced by the fact that 50% of the crash dumps for 2.26 are about this single bug ;)