Zugg Software :: View topic

Enchanter Joined: 09 Sep 2007 Posts: 605

Everything listed below can be left for later betas, just post it in order to not forget about them.
1) Create a push button. Push left mouse button while above the button and move mouse away. The button has got stuck in pressed position. Must click once more the button for it to execute associated script.
UPDATE: It seems this happens with all button types, not only with push buttons.
2) "Class Editor / Options / Sub menu class" option has wrong tooltip and status line help. It is a good reason finally read the manual, but better should be fixed. :)
3) Editor has different fonts for different settings edit script window. Aliases, functions, triggers,... - Courier New; variables and status lines - Arial (I suppose).

Posted: Fri Oct 05, 2007 6:30 pm

1) That one will be a bit hard to fix, but I'll add it to the low-priority list
2) Fixed.
3) Anything that has a "script" uses the script editor (aliases, functions, triggers,...). Anything that simply has a "value" (variable, status line) uses a text editor instead of a script editor, and Arial is used for that. This is normal. For example, you might store a long text message in a variable. So the Variable text editor is just like any normal "memo" field in Windows, along with spellchecking. Whereas for a "script", you need an editor with syntax highlighting, line numbers, etc, and that requires a fixed-space font (like Courier New) instead of the proportional font used for plain text.

Enchanter Joined: 09 Sep 2007 Posts: 605

About 3)
It's just a matter of psychology. :) I'm often stare at status line text, failing to recognize my own vars just because they shown with another font. Ok, if its impossible to change quickly control' font, ignore my 3).

Posted: Fri Oct 05, 2007 7:02 pm

With the status bars, I'm more likely to switch to the script editor in the future, since status bar items really are "scripts" in a way and it might be useful to have syntax checking for those.

Wizard Joined: 14 Aug 2004 Posts: 1269

Variables can contain scripts too! i.e. VARFUNCs.

Posted: Fri Oct 05, 2007 9:35 pm

Yes, I know that, but that is mainly for backwards compatibility with zMUD. For new applications I recommend the new #FUNCTIONs instead. Which is exactly why I changed the name of the command, even though it broke past compatibility. There is no speed improvement to using a #VARFUNC, so there really isn't much reason to use them anymore (except for compatibility). And the concept of a "variable" containing a "function" was just too weird for most people.

Wizard Joined: 14 Aug 2004 Posts: 1269

#VARFUNCs aren't compiled? If I look on the Compiled tab on some of my variables that were functions in zMUD, it's exactly the same as the Text tab...

Posted: Sat Oct 06, 2007 3:10 am

#VARFUNCs *are* compiled. Unless they are straight string or numeric values, in which case they will look the same as the Text tab. But if you use an expression, then you will get the compiled code.