Zugg Software :: View topic

Wizard Joined: 15 Jan 2002 Posts: 1644 Location: USA

Some of these may have been posted but I am going to consolidate them all in this post

Edit Session won't change the "session title" on an existing session, however as a work around you can <right click->rename> on the session icon to change it
Creating a session called "Mychar on Mymud" will create a "MycharonMymud.pkg" file in the "MycharonMymud" folder. I wish this was more zmud like with the addition of a Mudname field. Then when creating a new session it will use the Mudname field to create the folder and package name instead of the session title (however if this is blank it could default to using the session title). This will make it easier to create seperate sessions for one mud using the same folder/file http://forums.zuggsoft.com/phpbb/viewtopic.php?t=26907#107985
When using the %documents%\My Games\Cmud install choice everythiing work correctly for a while. Then defaults back to the cmud.exe location. this has been reported by a few people. (tested on XPsp2)
1. Create a new session MUDNAME MUDHOST MUDPORT
2. In the "%documents%\My Games\Cmud\MUDNAME" directory create a "Logs" directory
3. Connect to the session and type "#LOG Logs\Test.txt
4. Note that the log is correctly created in the "%documents%\My Games\Cmud\MUDNAME\Logs" Directory
5. Close Cmud restart the computer open cmud (this is very random on when it happens the problem is very reproducable however getting to the exact point of reproduction I am not certain about sometimes it works correctly for a week sometimes more)
6. Eventually it gets to the point where step C won't get created in the correct folder but if you were to make a Logs directory in your cmud.exe directory it will create it there (This happens with any command using relative directorys not just #log)
7. The session path is still correct as "%documents%\My Games\Cmud\MUDNAME" and The registry settings all show the correct setting as %documents%\My Games\Cmud Something in the cmud code is changing this internally :(
I am having a problem with #ALARMS created by one package not getting #UNTRIGGER/#SUSPENDED correctly from a triggered event
1. Create PKG A and PKG B, Pkg A contains mud window "A" Pkg B contains module "B"
2. In PKG B editor create 2 triggers
3. #1 Pattern:TESTON code:#ALARM "test" {+120} {#SHOW Times up!}
4. #2 Patten: TESTOFF code:#RAISE StopAlarms all
5. In PKG B create an EVENT
6. Name: StopAlarms code:#UNTRIGGER test
7. Type TESTON and a +120 second alarm is created in pkg A window A
8. Type TESTOFF you won't get a Trigger removed message
9. Type #ALARM it still shows a +120 alarm active and counting down
If triggers are off (#IG) active alarms keep counting down and will go into negative times and never fire untill reconnected.
#ADD Db.Var 1 syntax does not work (it will change the value of db.var to the value but won't add to it
The Settings Editor code editor needs a way to toggle wordwrap. I am not a fan of wordwrapped code!
The Settings Editor code window flickers if there is more then a screenfull of text and you are typing in it. This might change with the addition of the new editor component.
Hopefully the Editor window is also changed to use the scintilla editor component to provide syntax highlighting etc :p
I can't stand that the "enter" key closes the settings editor. Of course this prolly comes from using excel to move down a row/confirm data etc.
Functions that can create optional variables should have the ability to create a local variable instead. ex %match, %regex.

Posted: Mon Mar 26, 2007 6:27 pm

1) It's on the bug list

2) This was changed on purpose. I get lots of support issues from zMUD because zMUD shares the same folder/settings file for different characters on the same MUD. It's easy to select Edit Session and then use Browse to change the folder and filename of the PKG file if you want it to go into the same folder as another session.

3) The #LOG command isn't using the DataDir registry key. It's actually using the "Current working directory" in Windows. Usually the current working directory is set by the shortcut in Windows that you use to launch CMUD. But you might get the directory to change when using various File/Open or File/Save dialogs. Once the current directory is changed, then #LOG will use it. This same issue happens with the #FILE command, and most other commands that take a file name. Currently DataDir is only used when opening packages and sessions. This is on the bug list.

But if the error you reported is effecting packages or character settings, let me know. But the code is using the DataDir registry for that, so if the registry is still set properly, then I don't see any way for packages to get saved or loaded to the wrong place.

4) Settings created within a window are private to that window. So, when you use TESTON to create the alarm in Window A, the alarm is private within Window A. So, there is no way for your event in Package B to remove the "test" alarm that is stored in Window A. You'll need to figure out a different way to do this since this isn't a bug and it's working as designed.

5) Added to bug list.

6) Yes, there are several problems with commands that accept a variable name (#ADD, #ADDITEM, etc) that do not work with anything other than a simple variable name. Doesn't work with Db.Key as you mentioned...doesn't work with local variables, etc. This is on the bug list, but will take a while to get working because it's a pretty major parser issue that might have some bad side effects.

7) This is already fixed by the new code editor component for v1.27

8) This is already fixed by the new code editor.

9) Haven't decided about this yet. The Editor window is also designed to edit Notes and HTML files (something the code editor can't do). So I can't just replace the Editor with the new code editor component. I need to somehow merge the two so that the existing editor is used for text, HTML, and ANSI log files, while the new code editor is used for scripts. This probably won't appear until after 1.27. I want to get the bugs out of the code editor in the Package Editor before I start messing with the tabbed text Editor window.

10) "Enter" *always* activates the default button in a Windows dialog. You should be used to this in other Windows applications. You should be using the Tab key to move between fields. The idea of making the Package Editor work like a dialog (where Enter activates a hidden "OK" button and ESC activates a hidden "Cancel" button) allows people using the keyboard to save some time. For example, you can press Ctrl-A to create an alias, enter the alias definition and then press Enter to save and close the package editor.

Without doing this, keyboard users would not have an easy way to interact with the Package Editor, and I'm trying to make CMUD work better for keyboard users. Forcing the user to click the close button with the mouse is not acceptable to most keyboard users. So, I'm afraid you will just need to get used to this. Just think of the Package Editor as a normal Windows dialog with an OK/Cancel button. As with any other Windows dialog, pressing Enter is going to activate the OK button and close the window.

11) You can already do this. The %match and %regex functions already work with local variable names.

Wizard Joined: 15 Jan 2002 Posts: 1644 Location: USA

Thanks for clearing up alot of things.

I figured out how to handle #4 by creating it in the module using #ALARM "id" {time} {commands} "Modulename" syntax. which I prolly read somewhere here on the forums and forget right away.