Zugg Software :: View topic - What is needed to make v3.06 a Public Version?

Posted: Tue Mar 24, 2009 5:17 pm

Right now I'm still collecting bug reports for v3.05. I've only seen a couple of issues that I think are really high priorities for a public release (like the new quirks with the Remote MXP option, remaining issues with some ANSI and MXP colors and HTML logging). I also need to audit the crash dump database and check to see if there are any common crash problems that anyone has been reporting.

What do *you* think are the high-priority issues that need to be fixed for a new public version? I think it's getting pretty close. I'm probably going to wait at least another week to let more reports come in.

Posted: Tue Mar 24, 2009 6:22 pm

[3.05] Mapper Issues with %inwalk %walkactive %destroom and onWalkEnd
http://forums.zuggsoft.com/forums/viewtopic.php?t=33205

[3.05] Check Syntax not recognizing a local variable definition
http://forums.zuggsoft.com/forums/viewtopic.php?t=33057

[3.03a] Lines in window disappear then reappear as they scroll up.
http://forums.zuggsoft.com/forums/viewtopic.php?t=32734

[3.05] Syntax hilighting absent on sub-states unless you click on the main first
http://forums.zuggsoft.com/forums/viewtopic.php?t=33071

(fixed 3.08) [3.06] Flickering buttons
http://forums.zuggsoft.com/forums/viewtopic.php?t=33225

(fixed 3.06) [3.05] Scoping and the Mapper room enable/disable code
http://forums.zuggsoft.com/forums/viewtopic.php?t=33018

(fixed 3.06) [3.05] Weird copying of text in the disable tab of a map class folder
http://forums.zuggsoft.com/forums/viewtopic.php?t=33019

(fixed 3.06) [3.04] Finally found reproducable code to freeze/lockup Cmud
http://forums.zuggsoft.com/forums/viewtopic.php?t=32963

(fixed 3.06) [3.05] #capture and disappearing MXP colors after a prompt
http://forums.zuggsoft.com/forums/viewtopic.php?t=32991

(fixed 3.06) [3.04] #capture not working correctly with #cw
http://forums.zuggsoft.com/forums/viewtopic.php?t=32964

(fixed 3.06) [3.03a] #CW with #say has a bug
http://forums.zuggsoft.com/forums/viewtopic.php?t=32655

Apprentice Joined: 08 Dec 2005 Posts: 108

[3.05 Pro] Room properties does not display room properties on create. I think this is a biggie

Posted: Wed Mar 25, 2009 2:29 pm

Scoping with enable and disable, and errant script copying are problematic, and i think deserve highest priority as well as:

Undo feature messing up scripts.
http://forums.zuggsoft.com/forums/viewtopic.php?t=32823
Zugg, were you able to locate a method to clear the change stack?

Scoping with speedmenus and prompt
http://forums.zuggsoft.com/forums/viewtopic.php?t=32927

MXP, colors, syntax highlight and captures are also very important, but an annoyance.

All in all 3.05 has been fairly stable, and a vast improvement over 2.xx mapper
[/url]

Posted: Wed Mar 25, 2009 4:47 pm

Posted: Wed Apr 01, 2009 5:28 pm

Bumping this to get more feedback.

Posted: Wed Apr 01, 2009 6:39 pm

How goes the work?

Posted: Wed Apr 01, 2009 8:34 pm

Still working on bugs and new features, but I wanted to get more feedback from other people on what they thought needed to have a high priority to fix in the public version.

I'll be doing another beta release before the public version, either at the end of this week, or early next week. I have some new features that I wanted tested a bit before the public version.

Posted: Thu Apr 02, 2009 11:36 am

There've been a few threads around reporting problems relating to the new "only allow MXP from the server if the server negotiates MXP" option. Is there actually a bug there (and if so, is it already fixed?), or is it just that those servers never actually negotiated MXP?

Posted: Thu Apr 02, 2009 5:03 pm

The bug with that was if you caused a trigger to fire via the #SHOW command, then any MXP sent via #PRINT or #MXP in the trigger would not be processed. This is fixed in the next version so that #PRINT and #MXP always use the local MXP preference and not the RemoteMXP preference. However, any MXP used in a #SHOW command will not be processed unless the server negotiates MXP or the RemoteMXP option is enabled -- that is by design. I'll wait until after 3.06 is released to see if this fixed all of the reported problems with the new RemoteMXP option or not.

Posted: Fri Apr 03, 2009 3:32 pm

One of our cats passed away so I'm not going to get any version released this week. Hopefully I'll be able to get the next beta version out towards the end of next week.

Posted: Fri Apr 03, 2009 9:42 pm

My condolences on your loss. I lost one myself last month.

Posted: Sat Apr 04, 2009 6:41 pm

It is amazing how attached you get to pets. I was totally cut up about losing a Guinea Pig the other year, it quite surprised me.

Poor Potter family :( *cry*

Posted: Sat Apr 18, 2009 4:50 pm

I updated my list of bugs. All except three of them were fixed. To that list I added one I didn't have listed from 3.05 and a new bug regarding buttons from 3.06.

Posted: Mon Apr 20, 2009 5:26 pm

Thanks for updating your posts. It's always good for me to get confirmation that something is fixed. And thanks for editing your subjects to add "Fixed". When I first looked at the forums over the weekend, my initial reaction was "ACK!!" to all of the posts until I noticed that you were mostly reporting stuff that was fixed ;)

Posted: Mon Apr 20, 2009 6:07 pm

To be honest, posting on the threads that they were fixed was somewhat for me. I had posted so many bug reports I was getting confused as to which ones had been fixed. Marking them as fixed let me know that I had retested it and saw that it was working. But it should be good for any others that may come across a similar issue to see what the result was or for you to know that your fixes worked.

Good job on the fixes, you fixed a ton of stuff. The current version is very nice and functional for me.

Incidentally, I was looking through your comments on my retesting for 3.06. It looks like on various of them you hadn't intended them to be addressed in 3.06 and you consequently posted that they are still on the bug list. It is often times hard when looking at your change log to determine whether an item listed pertains to my particular post. In this last round of changes your work was so extensive that I didn't rule out from consideration any of my bug posts. If it wouldn't be too difficult could you add a link to the post that spawned the bug fix in the change-log? With that information I'd be able to retest only those things you intended to be fixed. However, the list of bugs for me is down to a mere handful so I don't mind retesting them all if it doesn't overly annoy you to see my retest messages.

Posted: Mon Apr 20, 2009 7:46 pm

I really don't want to tie the Version History with links to the forums at this time. Some bugs have multiple forum posts, some have entries in the crash-dump database, and some don't have any other link. Some day when I get time I'd still like to create a bug tracking system for the web site and then I can link the version history to proper bug entries in the database. But I just don't have the time to do something like that right now, sorry.

It's still useful to re-test other issues that you don't see in the version history since in many cases fixing one bug can cause several other related issues to get fixed. So it *is* useful for me to know which bugs are still not fixed, even when I don't specifically fix them in the version history.