Re: TR's Pathfinder Toolbar
Posted: Sun Aug 08, 2010 2:36 pm
I'll see about adding days some time this week, but for tonight, I have to GM (woe is me!)
I'm curious how that would work. I like the responsiveness of the buttons as well (ie if I don't have the dialog in focus when I click and it still goes off) I've not had much success in controlling <input type="image" since it appears to not let you scale the image. Can you put an image on a regular submit button? If so what does the html look like? Can you scale it with width/height?aliasmask wrote:I may go with form submit buttons with images because they're more responsive when clicked, but not necessarily better looking.
Instead of using an image for the link, it would be a submit button with an image. There are a couple of ways to do that, but putting html in the value of the submit it how I have done it.Sir Flak wrote:I'm curious how that would work. I like the responsiveness of the buttons as well (ie if I don't have the dialog in focus when I click and it still goes off) I've not had much success in controlling <input type="image" since it appears to not let you scale the image. Can you put an image on a regular submit button? If so what does the html look like? Can you scale it with width/height?aliasmask wrote:I may go with form submit buttons with images because they're more responsive when clicked, but not necessarily better looking.
Code: Select all
<input type="submit" value="<html><img src="assetId" height=xx width=xx></html>"></html>
Rumble posted a replacement Default.theme that fixes the button margins. Not sure if it's portable to anything other than Windows but if he didn't hard-code fonts it should be...aliasmask wrote:Because the built in button format are really skewed 12px margin, I used tinyLaf and default.theme to change that to 4px so button look a little better with text and images.
Thanks for the tip.aliasmask wrote:Instead of using an image for the link, it would be a submit button with an image. There are a couple of ways to do that, but putting html in the value of the submit it how I have done it.Sir Flak wrote:I'm curious how that would work. I like the responsiveness of the buttons as well (ie if I don't have the dialog in focus when I click and it still goes off) I've not had much success in controlling <input type="image" since it appears to not let you scale the image. Can you put an image on a regular submit button? If so what does the html look like? Can you scale it with width/height?aliasmask wrote:I may go with form submit buttons with images because they're more responsive when clicked, but not necessarily better looking.Because the built in button format are really skewed 12px margin, I used tinyLaf and default.theme to change that to 4px so button look a little better with text and images.Code: Select all
<input type="submit" value="<html><img src="assetId" height=xx width=xx></html>"></html>
Code: Select all
[H: Image=getTokenImage()]
<input type="submit" name="save" value="<html><img src='{Image}' height=32 width=32><html>"></input>
Code: Select all
[h: FormData = macro.args ]
[h: useDice = json.contains( FormData, "useDice" ) ]
[h: FRA = json.contains( FormData, "FRA" ) ]
[h: Flanking = json.contains( FormData, "Flanking" ) ]
[h: FE = json.contains( FormData, "FE" ) ]
[h: FE2 = json.contains( FormData, "FE2" ) ]
[h: FE3 = json.contains( FormData, "FE3" ) ]
[h: FE4 = json.contains( FormData, "FE4" ) ]
[h: FE5 = json.contains( FormData, "FE5" ) ]
[h: Smite = json.contains( FormData, "Smite" ) ]
[h: BSmite = json.contains( FormData, "BSmite" ) ]
[h: PowerAttack = json.contains( FormData, "PowerAttack" ) ]
[h: Charge = json.contains( FormData, "Charge" ) ]
[h: wTwoWeaponFighting = json.contains( FormData, "wTwoWeaponFighting" ) ]
[h: UseSecondary = json.contains( FormData, "UseSecondary" ) ]
[h: FOB = json.contains( FormData, "FOB" ) ]
[h: KFOB = json.contains( FormData, "KFOB" ) ]
[h: ArcaneStrike = json.contains( FormData, "ArcaneStrike" ) ]
[h: FightingDefensive = json.contains( FormData, "FightingDefensive" ) ]
[h: wCombatExpertise = json.contains( FormData, "wCombatExpertise" ) ]
[h: RacialHatred = json.contains( FormData, "RacialHatred" ) ]
[h: StunningFist = json.contains( FormData, "StunningFist" ) ]
[h: TA = json.contains( FormData, "TA" ) ]
[h: MFRA = json.contains( FormData, "MFRA" ) ]
[h: MFRAW=0]
[h: LayOnHands = json.contains( FormData, "LayOnHands" ) ]
[h: wSneak = json.contains( FormData, "Sneak" ) ]
[h: wKiDodge = json.contains( FormData, "wKiDodge" ) ]
[h: zMonsterWeapon = json.contains( FormData, "wMonsterWeapon" ) ]
[h: Demoralize = json.contains( FormData, "Demoralize" ) ]
[h: isMonster = json.contains( FormData, "isMonster" ) ]
[h: CombatMan = json.contains( FormData, "CM" ) ]
Code: Select all
[H: varsFromStrProp(json.toStrProp(FormData))]
Code: Select all
{"Flanking":"on","wCombatExpertise":"on","FOB":"on","wKiDodge":"on","CM":"0","MyAction":"Action"}
I am very interested in trying this but also very new to using MapTools as anything than just mapping software. I have all of the Tokens exported but am unclear on how to save a copy of the properties and then in turn import them into my campaign.toyrobots wrote:
To put it into another campaign file, save a copy of the Lib:PathfinderRPG token, the button image tokens (there are several of these in stacked) and the campaign properties. Then drop the lib and image tokens in your new campaign, and load the new properties. As long as you have the Libs, Images, and props, you're good to go.
All the properties are hidden and accessed through getProperty() and setProperty(), which is why you only see the one prop in the campaign props. They get initialized when you run the "setup token" button, so nothing will work until you have set up the token.
In the MapTools menu, go to Edit->Campaign Properties, and click "Export" near the lower left of the dialog box. "Import" is right next to it.Ozman51 wrote:I am very interested in trying this but also very new to using MapTools as anything than just mapping software. I have all of the Tokens exported but am unclear on how to save a copy of the properties and then in turn import them into my campaign.