This is a test piece to try my idea. The piece image “comes” from html code in a Text Label, and a Marker Trait with the image name saved in it.
Why? 'cause i want to show one image per each unit LifePoint, like this:
But i don’t want to create 4 different layers for each different unit (they are a lot). With this method (which is the only way i’ve found to use a property to pick an image) i can build just ONE prototype, and then just add the UnitImage Marker Trait to each differet unit piece.
What makes me … cautious is the Text Labels behaviour: in order to show that image i had to
- set a font size of “300”, and
- add two dots ( “..” ) at the end
or the longest images will be cropped.
Also, Text Labels tends to “move around” in the piece area depending on the trait order, in a way that i still have to understand.
So, my questions are:
- do the user font size settings (either in Vassal preferences, or in the OS settings) can affect the final result?
- There’s something to worry about general Vassal performances when about 30 units, each showing 3 or 4 times the images (so, 3 or 4 Text Label Traits with different offsets) are on the screen?
- How exactly a Text Label position is computed, in relation to traits order?
- There’s other reasons for which i should avoid this pratice?
Thanks