Changing the order of items listed in tables.
When I started working in Chill, I defaulted to listing the primary attributes in alphabetical order. I did not lost the derived traits in alphabetical order, but I don't recall why. Still, the reason isn't important.
Now, I'm working on some cosmetic changes to more closely match how things are listed on the official character sheet. I edited thing_attributes.dat, and simply changed the order of the attribute things. I reopened Hero Lab, and the order in which the attributes were now listed matched the changes I made in the .dat file. I then similarly edited thing_traits.dat. I reopened Hero Lab, and the order of the derived traits was no different than before. The order of appearance did not match my changes, nor was in alphabetical. I have no idea what's determining the order in which the derived traits are listed. Is it supposed to match the order in which I list them in the file? |
Assuming you're using a table to display them, it's based on the sortset (which does default to alphabetical). If you're explicitly building individual portals, it is of course according to how you did your position section.
|
Quote:
|
Oh man... I wish I could get it to do that on some of mine. :-P
Can you provide the code for how you're displaying it? |
Quote:
Code:
<document signature="Hero Lab Data"> Code:
<portal Code:
<template Code:
<layout WPR STA REF STU This doesn't match the order in thing_traits.dat, and it's not alphabetical. |
The current display matches the ORIGINAL order in which I listed them in thing_traits.dat. But after I changed the order, the display did not follow suit.
|
Just to be clear, the explicit tags you have (and setting the sort to explicit) indicates that you want the display to be
Those are the Explicit tags you have on them. |
Quote:
|
Quote:
|
Quote:
|
All times are GMT -8. The time now is 03:44 AM. |
Powered by vBulletin® - Copyright ©2000 - 2024, vBulletin Solutions, Inc.
wolflair.com copyright ©1998-2016 Lone Wolf Development, Inc. View our Privacy Policy here.