Senior Member
Volunteer Data File Contributor
Join Date: Nov 2009
Posts: 1,502
|
So, this may be a gimme thing, but I'm implementing the optional bits in the Planet Mercenary background and Command Packages where a given Command Package might have "+2 to Inspire or Entertain". I copied the code from 4E and how they allow races to apply a bonus to one ability for another, but I couldn't understand their "BuildLast" sort set, so I left it blank initially. Except... that means that the items rearrange as I fill in values to alphabetize by the chosen skill. Is there a good way to have it sort by the order I added the items so that they don't rearrange themselves? This is the relevant code:
Quote:
Quote:
Quote:
Quote:
Quote:
Yes, I know that I need to modify the logic here so that the items with only one choice don't display a list. Quote:
|
||||||
#1 |
Senior Member
Volunteer Data File Contributor
Join Date: Nov 2009
Posts: 1,502
|
Hmm... and I'm running into something I hadn't noticed before. The bootstrapped changes to #traitbase "stick". So if I get a +2 boost to Inspire from my background (bringing me up to 2 without any points spent on it), then switch to a background that doesn't give that bonus, it acts like I spent those two points. Given trtUser is being changed as well, I suspect I made a different error here. I'll look at it in the morning.
|
#2 |
Senior Member
Volunteer Data File Contributor
Join Date: Nov 2009
Posts: 1,502
|
And I've got it fixed, albeit by doing something completely different. ^_^
|
#3 |
Senior Member
Volunteer Data File Contributor
Join Date: Nov 2009
Posts: 1,502
|
The one oddity that I have seen happening is that, if a modification brings an item to the minimum or maximum value, the summary panel does not update for that item. So if I have five ranks and shift-click on the incrementor (changing the value by 5), the tab on the side doesn't update either way because the value is 0 (minimum) or 9 (maximum). The same thing happens for values modified with modify by a script. Maybe the fact that a tag is being assigned for Minimum or Maximum is interrupting it?
|
#4 |
Senior Member
Join Date: Mar 2013
Location: Greater London, UK
Posts: 2,623
|
Quote:
Farling Author of the Realm Works Import tool, Realm Works Output tool and Realm Works to Foundry module Donations gratefully received via Patreon, Ko-Fi or Paypal |
|
#5 |
Senior Member
Volunteer Data File Contributor
Join Date: Nov 2009
Posts: 1,502
|
Thanks for the tip, Farling. I just tried that, and it did not solve the problem. I will look into getting the relevant files publicly available so that others can look at it. The last time I tried zipping them up, it was just above the margin for attachments here, but I still have a fair amount of cruft from the skeleton files and my experiments. I do have it available via GitHub here if you'd like to take a look at the files themselves.
|
#6 |
Senior Member
Lone Wolf Staff
Join Date: May 2005
Posts: 13,213
|
You've got alwaysupdate="yes" on the summary table? I find that I just need to add that to all the summary tables - I'm not sure why the skeleton files don't just do that by default.
For order, add tags from the explicit group - explicit.1, explicit.2, etc., and then add a sort order to the table that looks for those tags. |
#7 |
Senior Member
Volunteer Data File Contributor
Join Date: Nov 2009
Posts: 1,502
|
Quote:
Quote:
Last edited by Duggan; August 24th, 2017 at 09:17 AM. |
||
#8 |
Senior Member
Volunteer Data File Contributor
Join Date: Nov 2009
Posts: 1,502
|
Silly question, is there any way to tell the system to not try to sort a table at all? Right now, I have Specialties that accept a typed-in value (Specifically, the case I'm staring at right now are the Xenobiology specialties where you can specify which world). If I start typing in one, and the value I type causes it to change location, I instead find myself typing in the field which gets sorted into that location. So, for example, if I had the following:
Quote:
Quote:
Code:
<sortset id="Feats" name="Feats by Tier"> <sortkey isfield="no" id="Tier"/> <sortkey isfield="no" id="_Name_"/> </sortset> |
||
#9 |
Senior Member
Lone Wolf Staff
Join Date: May 2005
Posts: 13,213
|
Check out the allowuserorder="yes" parameter on the table - would that work? They'd be fixed in place until the user moved the items, which would mean they wouldn't re-sort just because they were renamed.
|
#10 |
|
|