Build 16 fixes the issues brought up here:
That worked really nice the search there is one problem with it. When you Select a creature by checking the box (when searching) it does not pull up the correct creature, even if there is only one result.
About the bug, when I enter "game setting/combatant categorie" and try to add "Ennemie", I get "the index card url'file:/c:/documents and settings/jay/workspace/initiativetool/tests/resources/testForm.jfrm' could not be opened".
"Ennemies" is added to "NPC" and "PC" but whenever I click on it, I get the same error message.
It is reproductible on two windows PC.
And, much less of a problem, the "about initiative tool" menu opens up a big blank window.
In the end my needs are pretty straightforward. When adding a combatant from the Add Combatants dialog I need to be able to enter their Initiative value directly and have that value applied. I was trying to use Mod just because it was there.
You would enter the value in your phase sort property and it would work just like I think your asking. I know it was a long time ago (and I'm old
). but I'm pretty sure this is why we added the phase sort property. I think it does exactly what you are asking. If I were to rewrite IT I would probably just make the initiative value another custom property and then allow the GM to select the proper one. I can't go back and change it, but that would probably have been the best design. You should probably just hide the fields. You can do that everywhere but the index card. In my first build of IT 1.1 you will be able to change this too.
I added the ability to see the phase sort property on the index card for the next build. I did not change the table or list views to show the phase sort property. In the table view the phase sort property already has a column. In the list view it would require some way to identify that the value is not the initiative, and that made it look a bit busy again. Will the change to the index card be enough?
What I would like to see is that any combatant loaded from the default lookup use properties from that data to determine:
* Name - does this
* Category - sounds like it does this
* Player - doesn't do this? Really ought to default to GM.
Combatant fields --> lookup property names now --> in build 
name --> name --> name
category --> inittoolType --> itCategory
player --> N/A --> N/A
count --> N/A forced to 1 --> N/A forced to 1
initiative modifier --> initBonus --> itInitiativeModifier
notes --> N/A --> itNotes
token --> maptoolToken --> itToken
I thought it best to leave player blank and just assume that a null value is the GM which is how it works in the index cards. I could be pursuaded to change my mind though...
What about having the notes field automatically filled in if there is a corresponding notes property in the lookup file?
It is using the group combatant data structure, and I haven't added a notes property to it yet. There is a tracker for this, and since I forgot it originally I'll try to get it in the next build.