MapTool 1.1 Development Release Build 11
Moderators: dorpond, trevor, Azhrei, Craig
- trevor
- Codeum Arcanum (RPTools Founder)
- Posts: 11311
- Joined: Mon Jan 09, 2006 4:16 pm
- Location: Austin, Tx
- Contact:
MapTool 1.1 Development Release Build 11
Couldn't wait to get these new features out to you guys (and fix a Last Path bug) !
Build 11 (7/25/06)
* Restructure method to show/hide the command window
* Fix show last path and revert move bug on group moves
* Middle Mouse click during token move sets a waypoint
* Add macro buttons to command panel
The macro buttons are easy to use:
- Left click to execute
- Right click to set the command (drag-drop support to come later)
- Put a '/' at the end of the command to cause immediate execution (fake an ENTER key at the end)
- Hover over for a tooltip that will show the command text
- Gray buttons are unassigned, orange buttons have a command
NOTE: The commands are not saved at the moment. We need to decide WHERE to put the commands.
Build 11 (7/25/06)
* Restructure method to show/hide the command window
* Fix show last path and revert move bug on group moves
* Middle Mouse click during token move sets a waypoint
* Add macro buttons to command panel
The macro buttons are easy to use:
- Left click to execute
- Right click to set the command (drag-drop support to come later)
- Put a '/' at the end of the command to cause immediate execution (fake an ENTER key at the end)
- Hover over for a tooltip that will show the command text
- Gray buttons are unassigned, orange buttons have a command
NOTE: The commands are not saved at the moment. We need to decide WHERE to put the commands.
Dreaming of a 1.3 release
-
- Dragon
- Posts: 780
- Joined: Tue Jan 31, 2006 9:01 pm
- Location: Beneath the Aurora Borealis
- Contact:
Good Stuff!
The macro buttons are pretty neat
When you left click to execute, it simply puts the command into the chat box, so you still have to hit enter to have it execute... is this intentional?
I know we can use aliases to speak as the token, but perhaps it would be easier to simply hilight a token and then the applicable commands will be performed "as" that token...
I do like the macro buttons... will speed up chat a whole lot!
The macro buttons are pretty neat
When you left click to execute, it simply puts the command into the chat box, so you still have to hit enter to have it execute... is this intentional?
I know we can use aliases to speak as the token, but perhaps it would be easier to simply hilight a token and then the applicable commands will be performed "as" that token...
I do like the macro buttons... will speed up chat a whole lot!
I haven't tried this new version yet but didn't Trevor say "Put a '/' at the end of the command to cause immediate execution (fake an ENTER key at the end)"?Emryys wrote:When you left click to execute, it simply puts the command into the chat box, so you still have to hit enter to have it execute... is this intentional?
Give it a try perhaps..
First:
This rocks. THANK YOU!
Yep, a slash / at the end does an enter.
I think the alias file would be a good place for the buttons so you can share and edit easily. Currently the alias file uses a : to seperate the alias from the command. You could use another symbol like # to define a button command, then modify load alias/save alias to load and save buttons as well.
Something like this creates a button and an alias
1#/say Trevor Rocks
ro:/say Rock On
Also, the ability to rename buttons would be nice as well.
Edit:
If buttons are in the alias file, then the buttons are created in the order they exist in the file. One with the same name overwrites and existing buttons definition, something with a new name gets the first unassigned button.
Assigning a button via chat would also come in handy. It should work a lot like the alias command. This would be mostly used for scripting but has some uses in real time so you can up arrow and change a button def on the fly.
Button defs in the alias file could get even more interesting if you start allowing property defs in the like forground and background colors. If you allow for properties, the button name could be one of those so the button identifier keeps 1,2,3,4,5,etc. This way the player has a bit more control over which botton gets what values both in the alias file and 'on the fly' creation'
yet another 2 cents,
Troll
This rocks. THANK YOU!
Yep, a slash / at the end does an enter.
I think the alias file would be a good place for the buttons so you can share and edit easily. Currently the alias file uses a : to seperate the alias from the command. You could use another symbol like # to define a button command, then modify load alias/save alias to load and save buttons as well.
Something like this creates a button and an alias
1#/say Trevor Rocks
ro:/say Rock On
Also, the ability to rename buttons would be nice as well.
Edit:
If buttons are in the alias file, then the buttons are created in the order they exist in the file. One with the same name overwrites and existing buttons definition, something with a new name gets the first unassigned button.
Assigning a button via chat would also come in handy. It should work a lot like the alias command. This would be mostly used for scripting but has some uses in real time so you can up arrow and change a button def on the fly.
Button defs in the alias file could get even more interesting if you start allowing property defs in the like forground and background colors. If you allow for properties, the button name could be one of those so the button identifier keeps 1,2,3,4,5,etc. This way the player has a bit more control over which botton gets what values both in the alias file and 'on the fly' creation'
yet another 2 cents,
Troll
- trevor
- Codeum Arcanum (RPTools Founder)
- Posts: 11311
- Joined: Mon Jan 09, 2006 4:16 pm
- Location: Austin, Tx
- Contact:
I had thought of making the labels editable, but then it occured to me that you would run out of horizontal space very quickly.
I thought maybe support icons instead, but then what icons would be used ? It seemed just as ambiguous as the numbers.
Numbers seemed to take the least amount of space, allowing for the maximum number of buttons to be viewable.
But I'm fully open to discussing how to make the buttons more usable.
I thought maybe support icons instead, but then what icons would be used ? It seemed just as ambiguous as the numbers.
Numbers seemed to take the least amount of space, allowing for the maximum number of buttons to be viewable.
But I'm fully open to discussing how to make the buttons more usable.
Dreaming of a 1.3 release
The issue with numbers is that I'll forget what's assigned to them. My plan is to take the NPC's assign attack and damage rolls then addin the monsters as well. By the time I get to 18 buttons there's no way I'll remember what's there. I would use one or two letters as a reminder so that 'Valathe Attack' would show up as VA on the button lable.
I also had the thought of icons on the buttons as an optional property. That way you could put a shrunk down token on there so you can remember what's programmed on the button at a glance but thought that was asking a bit much.
I also had the thought of icons on the buttons as an optional property. That way you could put a shrunk down token on there so you can remember what's programmed on the button at a glance but thought that was asking a bit much.
I think that maptool now has enough settings to have it create some sort of special file in it's directory to save them all in one place, so that you have a complete list of all your aliases, your settings, custom states, macros, the works all in one place. just a suggestion.
Chaotic Neutral means never having to say you're sorry.
- trevor
- Codeum Arcanum (RPTools Founder)
- Posts: 11311
- Joined: Mon Jan 09, 2006 4:16 pm
- Location: Austin, Tx
- Contact:
And a good one. I was starting to think the same thing. I was thinking of doing something like Eclipse does with Export. That is, you say something like File->Export, which brings up a wizard. in our case it will be preferences, and it will ask which preferences do you want to export:brisingre wrote:I think that maptool now has enough settings to have it create some sort of special file in it's directory to save them all in one place, so that you have a complete list of all your aliases, your settings, custom states, macros, the works all in one place. just a suggestion.
- UI layout
- Aliases
- Chat macros
- whatever
So you can selectively pick which items you want to export to a file. Then there would be a corresponding import that would load the file.
Dreaming of a 1.3 release