I can confirm this “text label bug” because I think is the same I was talking about a few weeks ago in this thread:
[url]https://forum.vassalengine.org/t/text-labels-bug/4630/1]
Tim,
This behavior/bug (choose the one you prefer) has been there for a long time.
The 3 screen captures I uploaded are only partial captures of the full piece. Here after is a screencapture with both the complete piece as seen in Editor and in the background as seen within the game:
Dumb question of the day: If the 3 bugs I reported previously in this thread also affect 3.1.8 and 3.1.9, do I have to open other bug report for those versions as well? Because I think that having them reported on 3.2.0 will not get them processed anytime soon.
Actually, if they exist prior to 3.2, the developers prefer that you change the ‘Version’ field in the tracker to 3.1.18, to expedite the release of 3.2 - and therefore the resolution of your bugs.
-Seth
Aye Aye Sir!
I shall do so this evening (GMT+1). I still have old versions of my modules I can test using 3.1.8 and 3.1.9.
I will edit the bugs and select the lowest version affected by those bugs.
Thus spake Aradiel:
Dumb question of the day: If the 3 bugs I reported previously in this
thread also affect 3.1.8 and 3.1.9, do I have to open other bug report
for those versions as well? Because I think that having them reported on
3.2.0 will not get them processed anytime soon.
I suppse you mean 3.1.18? In that case, you should set the versoin in
the bug report to 3.1.18.
–
J.
messages mailing list
messages@vassalengine.org
vassalengine.org/mailman/listinfo/messages
Oops… you’re right. I meant 3.1.18
I did load 3.1.18 and used a test module. I update the 4322 bug (see latest comment) and uploaded the test module on my web site. Link included in the bug report.
Bug report also updated for 4324 bug (select unit border offset)
Thus spake Aradiel:
Hello,
I filed 3 bugs for 3.2.0 and I would like to know if that’s all I have
to do or should I report them in this part of the forum along with
details about those bugs? (One of them is a bug that has been there for
a long time and persists in 3.2.0: I already filed a but report in the
old system on SourceForge under the “aradiel” nickname)
Please don’t file bugs on SourceForge. No one will ever see them there.
–
J.
messages mailing list
messages@vassalengine.org
vassalengine.org/mailman/listinfo/messages
Joel,
By “[…] I already filed a but report in the old system on SourceForge […]” I meant that when Sourceforge was still our bug tracking tool, I filed a bug report for the selected piece border problem.
Now that we use a new system and since the problem persists in 3.1.18/3.1.19/3.2.0, I filed a new report in our new system 
Bug 4268 (and it looks like 4122 might be the same bug) is a show stopper for me. Because of it I’ve been stuck at build 7890, the last build I’m aware of that didn’t have the bug. Is anyone looking at this?
Thanks,
-Mark R.
Thus spake Aradiel:
Joel,
By “[…] I already filed a but report in the old system on SourceForge
[…]” I meant that when Sourceforge was still our bug tracking tool, I
filed a bug report for the selected piece border problem.Now that we use a new system and since the problem persists in
3.1.18/3.1.19/3.2.0, I filed a new report in our new system
Ah, I see. When we switched over, all the old bugs were migrated. This
is ok. I didn’t want to leave you thinking that putting new bugs into
SF was the way to do it.
–
J.
messages mailing list
messages@vassalengine.org
vassalengine.org/mailman/listinfo/messages
Thus spake mroyer:
Bug 4268 (and it looks like 4122 might be the same bug) is a show
stopper for me. Because of it I’ve been stuck at build 7890, the last
build I’m aware of that didn’t have the bug. Is anyone looking at this?
I’ve poked Pieter about fixing this, as it’s apparently due to changes
he made to how hex grids are handled.
–
J.
messages mailing list
messages@vassalengine.org
vassalengine.org/mailman/listinfo/messages