I have several text fields that display counts of items in a deck. I originally left the background color as “nil”. It was only in the release of 3.1 that the problem occurred. The problem did not occur with any of 3.1 betas (which I used.) Is this known problem or should I update my model. Black on black is difficult to read.
Thus spake “dcholtx”:
I believe this is a bug. A nil background should be transparent. We’ll look
into this for 3.1.1.
–
J.
Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org
Post generated using Mail2Forum (mail2forum.com)
My text fields which also display count of a deck using a nil bg’s remained
transparent in 3.1
Post generated using Mail2Forum (mail2forum.com)
These fields were added in 3.1 beta, and therefore were not converted from 3.0 module. Could that make a difference?
On side note recreating them works.
Problem has reappeared. Recreating the text label no longer fixes the problem.
Thus spake “dcholtx”:
Brent, do you have any insight into this one?
–
J.
Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org
Post generated using Mail2Forum (mail2forum.com)
looking at this further I released that the problem is zoom dependent. The nil works at full size, but at any zoom level smaller the nil background is render as black.
Try toggling “High-quality scaling” in your module preferences.
- M.
2009/3/26 dcholtx <messages@forums.vassalengine.org (messages@forums.vassalengine.org)>
Post generated using Mail2Forum (mail2forum.com)
The problem is solv’ed. Thanks for your help. Because of the image caching problem, I had turned off high scale image quality long ago. I also noticed the memory map file option, and have turned that on as well. Assuming I have a large enough stack size, I would imagine that this will speed play?
Thus spake “dcholtx”:
That explains why I was never able to reproduce the problem. Now we’ll
have a better chance of solving it.
You should be able to run with a somewhat smaller maximum heap with
memory-mapped images turned on. It will make initial image loading take
longer. It will probably make map painting slightly faster on average
(because you’ll have fewer cache misses) but will also increase the
variance (because when you do have cache misses, they’ll take longer to
be made good).
–
J.
Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org
Post generated using Mail2Forum (mail2forum.com)