 |
oldguy2
Wizard
Joined: 17 Jun 2006
Posts: 1201
|
 Posted: Wed Jul 01, 2009 9:54 pm
Questions about 3.08
|
I have a few questions as I am going through all the beta version changes.
3.07 version
| Quote: |
Added: Button text colors for button states
Added: Button border colors for all states
Added: Background colors for button panels |
I love this. However, would it be possible to add a border to the button panels or change the height or width of panels? The reason being if you have two panels next to each other I would like to add a border on the side they touch or make them taller or wider. If not, then no big deal. My reason is that when I put two panels stacked on top of each other to make it look like one big panel the buttons control the height of the panel itself so when I try to layout all the buttons all neatly with the new styles the ones with borders look like they are overlapping and touching the other buttons because the panels touch each other. Sort of imagine a web page where you have a label and text box like label: [ ]. With the new styles I can make it look like that and then have stuff appear in the button with the border. Except my buttons below that have borders end up touching the button above and it all runs together if that makes sense, and it doesn't look very good. I'm not complaining here, just simply asking.
| Quote: |
| Fixed major bug preventing #NNN syntax from working in previous version |
This still shows as an error in the script if you use that syntax. After I changed them all to #loop n the error went away.
3.06 version
| Quote: |
| Added: Free-floating buttons. Set the Toolbar number to zero to place buttons over the main MUD window instead of docked to a button panel |
No question really. Just wanted to say this is really nice.
| Quote: |
| Added: User-defined styles via #STYLE and #NOSTYLE command. Color commands (#CW, #COLOR, #PCOL) recognize the name of a style in place of a color name. Styles edited in the Preferences dialog, or by adding View/Show/Styles in package editor. |
I have no clue how to use the new #style and #nostyle commands. If you add them in the script box, they show up as red? What is the full syntax?
| Quote: |
| Added: Ported simple trigger wizard from zMUD |
I'm not sure if this isn't finished or what, but I was looking at all the new stuff and noticed when you open this wizard it asks you to select on of the triggers below from the listbox and click next. However, the listbox is empty and there is nothing to select.
That is just a couple of things I had questions on. Thanks.
Also I noticed most everything on your new To-Do List that I had concerns about.  |
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Wed Jul 01, 2009 11:02 pm
|
| Quote: |
| However, would it be possible to add a border to the button panels or change the height or width of panels? |
Unfortunately not. The height and width of panels are automatically computed based upon the buttons stored within them. Overridding this would make it too easy to have buttons that don't get displayed because they are off the edge of the panel, which would cause support headaches. However, the issue with button borders overlapping sounds like a bug. It's possible the panel size is not taking the button border into consideration. The buttons *do* kludge their position a bit to make adjacent buttons overlap by one pixel so that borders are not "doubled" between adjacent buttons, so maybe that's it.
In any case, the kind of control over the button layout you are asking for just isn't available within the current panel system. You'd either need to wait until zApp forms are added (unfortunately, far in the future), or use the floating buttons to position your buttons more precisely within the main MUD window (although then you lose the panel background). You're just asking for stuff way beyond what was intended with the current simple button layout, sorry.
| Quote: |
| Fixed major bug preventing #NNN syntax from working in previous version |
There is still a known (and reported) bug in 3.08 when using #NNN within a block, like an #IF statement, so maybe that's what you encountered. It's already fixed for the next version.
| Quote: |
| I have no clue how to use the new #style and #nostyle commands |
Documentation for new commands is added right before a public release. But basically, the syntax is:
#STYLE Name "definition"
where the "definition" is a style format taken from the STYLES.INI file that is used by the syntax highlighting editor. It handles a simple syntax of "color", or "foreground,background", or "foreground,background,attribute" (where "attribute" is "bold", "italic", "underline", etc). For font name changes, then you need to put a syntax of "font:name" or "size:fontsize". The colors have an optional "fore:color" and "back:color" syntax, but when the name in front of the colon is omitted, CMUD assumes the first unnamed argument is the foreground color and the second unnamed argument is the background color.
v3.08 doesn't yet allow the "Name" to be a style number, so you can't change the default system styles with this command yet...you can only change the styles listed in the "User Defined" styles.
For example:
#STYLE MyStyle "red,blue"
#TRIGGER {test} {#CW MyStyle}
#SHOW This is a test
would color "test" with red on a blue background.
| Quote: |
| Added: Ported simple trigger wizard from zMUD |
You need a wizard configuration file. The one from zMUD was called zmud.wiz. There isn't any default wizard file included with CMUD yet. But if you have zMUD installed, you can rename the zmud.wiz file to cmud.wiz and put it into your CMUD data files and then it will be loaded. I'll add a default wizard file to the installer of the next version.
But in general, not many wizards were ever written for zMUD, which is why I postponed implementing this feature for so long. This feature won't really be very useful until I add the ability to store other files in the Shared Library (like mapper configurations), so then I'll be able to store wizards in the library. So look for this during the Mapper Phase 2 work. |
|
|
|
|
oldguy2
Wizard
Joined: 17 Jun 2006
Posts: 1201
|
Posted: Thu Jul 02, 2009 2:10 am
|
| Quote: |
#STYLE MyStyle "red,blue"
#TRIGGER {test} {#CW MyStyle}
#SHOW This is a test |
Ahhhh can we do that now? That's nice. I was wondering how I add my own styles. Basically it is like using constants. What is the #nostyle for? Does that delete the style you created or just stick that in a script where you don't want any style at all like pre formatted text for a code box?
| Quote: |
| You're just asking for stuff way beyond what was intended with the current simple button layout, sorry. |
For the toolbars, I just added a spacer button that is the same color as the toolbar so it is invisible, but made it a little higher or wider than the buttons and that made it look like the whole toolbar is taller or wider than the actual buttons since you can adjust the buttons from the top and move them down a little.
Also on the trigger wizard, I don't use it but was just pointing that out. Thanks for the explanation though. |
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Thu Jul 02, 2009 4:23 pm
|
The #nostyle deletes a style. I think it was supposed to be #unstyle, so that might change.
| Quote: |
| I just added a spacer button that is the same color as the toolbar so it is invisible |
Heh, I was just going to come post to this thread this morning to suggest doing exactly that! Adding a separator/spacer to the end of your buttons to adjust the height of the toolbar is exactly what you want to do to trick the system. Glad you already thought of it. |
|
|
|
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
