Vassal bug or Apple problem?

Technical Support & Bugs
1

I am working on a module. I am designing it in 3.2.15.

I have an inventory window that shows the card image in it. I attached a picture of what it looks like. On the left is how I see it. On the right is how another user sees it:

boardgamegeek.com/image/314 … e=original

I am using Windows 7 with Java 7 Update 17. Since he is the one having the problems, here is his computer info:

Model: Mac Pro 4,1 tower (2009)
OS: El Capitan (OS X 10.11.6)
CPU: 2.66 quad-core Intel Xeon
Memory: 16GB
Video: Nvidia Geforce GT 120
Vassal: 3.2.16
Java: 1.8.0_101

He said he sees the same behavior on a newer Macbook pro (2014) with an Nvidia Geforce GT 750 as well.

I didn’t do anything fancy in the module for this: it is a standard inventory window with a 0.7 zoom on a 407 x 555 pixel image.

Are you aware of this problem and is it an Apple problem?

Thanks

2

Thus spake airjudden:

I am working on a module. I am designing it in 3.2.15.

I have an inventory window that shows the card image in it. I attached a
picture of what it looks like. On the left is how I see it. On the right
is how another user sees it:

boardgamegeek.com/image/314[1] … e=original

I am using Windows 7 with Java 7 Update 17. Since he is the one having
the problems, here is his computer info:

Model: Mac Pro 4,1 tower (2009)
OS: El Capitan (OS X 10.11.6)
CPU: 2.66 quad-core Intel Xeon
Memory: 16GB
Video: Nvidia Geforce GT 120
Vassal: 3.2.16
Java: 1.8.0_101

He said he sees the same behavior on a newer Macbook pro (2014) with an
Nvidia Geforce GT 750 as well.

I didn’t do anything fancy in the module for this: it is a standard
inventory window with a 0.7 zoom on a 407 x 555 pixel image.

Are you aware of this problem and is it an Apple problem?

Thanks

[1] boardgamegeek.com/image/314

It’s the first I’ve seen that. Any cross-platform display differences
are almost certainly donw to Java or the OS.

–
J.

3

Hi, I’m the guy seeing this problem on my Mac.

Can you tell what type of widget is being used here? It seems like there must be some quirk of whatever widget is being used for OS X.

Dan