Twilight Struggle Deluxe card text problem

Tried the plist in VASSAL 3.1.14 on my PPC machine, same result. No text.

B

Okay, try this one:

myweb.dal.ca/mkiefte/Info.plist

(same URL).

  • M.

On 1 September 2010 08:46, bdgza bdegroot@gmail.com wrote:

Tried the plist in VASSAL 3.1.14 on my PPC machine, same result. No
text.

Okay, try this one:

bdegroot@gmail.com> wrote:

Tried the plist in VASSAL 3.1.14 on my PPC machine, same result. No
text.

You might have to clear your cache. It has the same file name.

  • M.

On 1 September 2010 09:27, Michael Kiefte mkiefte@dal.ca wrote:

Okay, try this one:

myweb.dal.ca/mkiefte/Info.plist

(same URL).

  • M.

On 1 September 2010 08:46, bdgza bdegroot@gmail.com wrote:

Tried the plist in VASSAL 3.1.14 on my PPC machine, same result. No
text.

You might have to clear your cache.� It has the same file name.

- M.

On 1 September 2010 09:27, Michael Kiefte <mkiefte@dal.ca> wrote:

Okay, try this one:(same URL).

- M.


On 1 September 2010 08:46, bdgza <[bdegroot@gmail.com](mailto:bdegroot@gmail.com)> wrote:
Tried the plist in VASSAL 3.1.14 on my PPC machine, same result. No
text.


I seriously doubt VASSAL would be caching the Info.plist file, but if it does, where?

I was referring to your web browser as, evidently, the first one didn’t
work.

Make sure that the actual, Info.plist gets updated. You can double click on
it to view its properties. You should see below under Java->Properties a
line like:

apple.awt.graphics.UseQuartz false

  • M.

On 1 September 2010 09:41, bdgza bdegroot@gmail.com wrote:

“mkiefte” wrote:

You might have to clear your cache. It has the same file name.

  • M.

I seriously doubt VASSAL would be caching the Info.plist file, but if it
does, where?

I was referring to your web browser as, evidently, the first one didn’t work.

Make sure that the actual, Info.plist gets updated.� You can double click on it to view its properties.� You should see below under Java->Properties a line like:


apple.awt.graphics.UseQuartz���������������� false

- M.

On 1 September 2010 09:41, bdgza <bdegroot@gmail.com> wrote:


"mkiefte" wrote:
You might have to clear your cache. �It has the same file name.

- M.




I seriously doubt VASSAL would be caching the Info.plist file, but if it
does, where?

Yes, UseQuartz off is in the plist. It doesn’t help.

The image you attached is of the old one though. The new one should have:

apple.awt.graphics.UseQuartz
false

Frankly, I don’t know if this makes a difference but give it a go.

  • M.

On 1 September 2010 10:27, bdgza bdegroot@gmail.com wrote:

Yes, UseQuartz off is in the plist. It doesn’t help.

[1]

“mkiefte” wrote:

I was referring to your web browser as, evidently, the first one
didn’t
work.

Make sure that the actual, Info.plist gets updated. You can double
click on
it to view its properties. You should see below under
Java->Properties a
line like:

apple.awt.graphics.UseQuartz false

  • M.

On 1 September 2010 09:41, bdgza wrote:

“mkiefte” wrote:

You might have to clear your cache. It has the same file name.

  • M.

I seriously doubt VASSAL would be caching the Info.plist file, but
if it
does, where?

I was referring to your web browser as, evidently, the first one
didn’t work.Make sure that the actual, Info.plist gets updated.� You
can double click on it to view its properties.� You should see below
under Java->Properties a line like:

apple.awt.graphics.UseQuartz����������������

false- M.On 1 September 2010 09:41, bdgza bdegroot@gmail.com wrote:

“mkiefte” wrote:

You might have to clear your cache. �It has the same file name.

  • M.

I seriously doubt VASSAL would be caching the Info.plist file, but if
it
does, where?

[1]
lh6.ggpht.com/_sOK1fYgjvQM/TH5Uk … quartz.jpg

The image you attached is of the old one though. The new one should have:

apple.awt.graphics.UseQuartz
false

Frankly, I don’t know if this makes a difference but give it a go.


- M.

On 1 September 2010 10:27, bdgza <bdegroot@gmail.com> wrote:

Yes, UseQuartz off is in the plist. It doesn’t help.



[1]







“mkiefte” wrote:

I was referring to your web browser as, evidently, the first one
didn't
work.

Make sure that the actual, Info.plist gets updated. You can double
click on
it to view its properties. You should see below under
Java->Properties a
line like:

apple.awt.graphics.UseQuartz false

- M.

On 1 September 2010 09:41, bdgza wrote:

>
> "mkiefte" wrote:
>
>> You might have to clear your cache. It has the same file name.
>>
>> - M.
>>
>>
>>
>
> I seriously doubt VASSAL would be caching the Info.plist file, but
if it
> does, where?
>
>

I was referring to your web browser as, evidently, the first one
didn't work.Make sure that the actual, Info.plist gets updated.� You
can double click on it to view its properties.� You should see below
under Java->Properties a line like:

apple.awt.graphics.UseQuartz����������������
false- M.On 1 September 2010 09:41, bdgza <[bdegroot@gmail.com](mailto:bdegroot@gmail.com)> wrote:

"mkiefte" wrote:

You might have to clear your cache. �It has the same file name.

- M.





I seriously doubt VASSAL would be caching the Info.plist file, but if
it
does, where?


[1] [lh6.ggpht.com/_sOK1fYgjvQM/TH5Uk ... quartz.jpg](http://lh6.ggpht.com/_sOK1fYgjvQM/TH5UkhptRQI/AAAAAAAAAv0/nx9IDJGjepI/s1152/ts-quartz.jpg)

The image clearly shows:
apple.awt.graphics.UseQuartz

Where else do you want that key?

http://lh4.ggpht.com/_sOK1fYgjvQM/TH6M8oZ3lqI/AAAAAAAAAwI/JDjt9QHqpLQ/ts-quartz2.jpg

Yes, I see that. But there is a subtle difference between that and:

apple.awt.graphics.UseQuartz
false

Again, I don’t know if it actually does make a difference. I don’t know how
the XML file is interpreted.

  • M.

On 1 September 2010 14:30, bdgza bdegroot@gmail.com wrote:

“mkiefte” wrote:

The image you attached is of the old one though. The new one should
have:

apple.awt.graphics.UseQuartz
false

Frankly, I don’t know if this makes a difference but give it a go.

The image clearly shows:

apple.awt.graphics.UseQuartz

Where else do you want that key?

lh4.ggpht.com/_sOK1fYgjvQM/TH6M8 … uartz2.jpg
[1]

[1]
lh4.ggpht.com/_sOK1fYgjvQM/TH6M8 … uartz2.jpg

Yes, I see that.� But there is a subtle difference between that and:


apple.awt.graphics.UseQuartz

false

Again, I don’t know if it actually does make a difference.� I don’t know how the XML file is interpreted.

- M.


On 1 September 2010 14:30, bdgza <bdegroot@gmail.com> wrote:


"mkiefte" wrote:
The image you attached is of the old one though. �The new one should
have:

apple.awt.graphics.UseQuartz
false

Frankly, I don't know if this makes a difference but give it a go.



The image clearly shows:

apple.awt.graphics.UseQuartz


Where else do you want that key?

[lh4.ggpht.com/_sOK1fYgjvQM/TH6M8 ... uartz2.jpg](http://lh4.ggpht.com/_sOK1fYgjvQM/TH6M8oZ3lqI/AAAAAAAAAwI/JDjt9QHqpLQ/ts-quartz2.jpg)
[1]

[1] [lh4.ggpht.com/_sOK1fYgjvQM/TH6M8 ... uartz2.jpg](http://lh4.ggpht.com/_sOK1fYgjvQM/TH6M8oZ3lqI/AAAAAAAAAwI/JDjt9QHqpLQ/ts-quartz2.jpg)



I tried both info.plist files linked, and on my PPC machine, still no go. Curiousity brings me to ask if anyone can test it using an Intel machine and 10.5.8? Is this most certainly a problem with the version of Java used in OS X 10.5.8?

Come to think of it, I think I may be able to boot my Intel machine using 10.5.8, I’ll post results later.

Arrgggghhh…

Here’s a link to the problem:

nanoant.com/apple/leopards-j … -rendering

Could you try running VASSAL from the command line? Go to your VASSAL-3.1.14
directory in the shell and type:

java -Dapple.awt.graphics.UseQuartz=false -classpath lib/Vengine.jar
VASSAL.launch.ModuleManager

However, the website seems to indicate that Quartz is not the default
pipeline…

If you feel really up to it, could you also go through that webpage and try
out their example to reproduce the problem outside of VASSAL. Again, I
can’t do this – everything works fine on my Macbook.

  • M.

On 1 September 2010 19:59, Kingcake matthewguidry@gmail.com wrote:

I tried both info.plist files linked, and on my PPC machine, still no
go. Curiousity brings me to ask if anyone can test it using an Intel
machine and 10.5.8? Is this most certainly a problem with the version
of Java used in OS X 10.5.8?
Come to think of it, I think I may be able to boot my Intel machine
using 10.5.8, I’ll post results later.

Arrgggghhh…

Here’s a link to the problem:

nanoant.com/apple/leopards-j … -rendering


Could you try running VASSAL from the command line? Go to your VASSAL-3.1.14 directory in the shell and type:

java -Dapple.awt.graphics.UseQuartz=false -classpath lib/Vengine.jar VASSAL.launch.ModuleManager


However, the website seems to indicate that Quartz is not the default pipeline…�

If you feel really up to it, could you also go through that webpage and try out their example to reproduce the problem outside of VASSAL.� Again, I can’t do this – everything works fine on my Macbook.


- M.

On 1 September 2010 19:59, Kingcake <matthewguidry@gmail.com> wrote:

I tried both info.plist files linked, and on my PPC machine, still no

go. �Curiousity brings me to ask if anyone can test it using an Intel

machine and 10.5.8? �Is this most certainly a problem with the version

of Java used in OS X 10.5.8? �

Come to think of it, I think I may be able to boot my Intel machine

using 10.5.8, I’ll post results later.


I tried the batik example, and the sample text only gets rendered properly with UseQuartz=off. I tried running VASSAL form the command line, but I still get the no-text problem in Twilight Struggle. My guess is that if it works, the UseQuartz perhaps doesn’t get passed on when the module manager launches the child process? I tried launching the player directly, but don’t have enough experience with how the player gets told which module to launch with, so it wouldn’t load anything.

I tried the batik example, and the sample text only gets rendered
properly with UseQuartz=off.

“off” or “false”?

I tried running VASSAL form the command
line, but I still get the no-text problem in Twilight Struggle. My guess
is that if it works, the UseQuartz perhaps doesn’t get passed on when
the module manager launches the child process?

That is entirely possible. I’ll have to look into it.

  • M.

I tried launching the
player directly, but don’t have enough experience with how the player
gets told which module to launch with, so it wouldn’t load anything.

[1]
nanoant.com/apple/leopards-j … -rendering




I tried the batik example, and the sample text only gets rendered
properly with UseQuartz=off.

"off" or "false"?

I tried running VASSAL form the command
line, but I still get the no-text problem in Twilight Struggle. My guess
is that if it works, the UseQuartz perhaps doesn't get passed on when
the module manager launches the child process?

That is entirely possible. I'll have to look into it.

- M.

I tried launching the
player directly, but don't have enough experience with how the player
gets told which module to launch with, so it wouldn't load anything.

[1] [nanoant.com/apple/leopards-j ... -rendering](http://www.nanoant.com/apple/leopards-java-105-update-2-breaks-quartz-pipeline-font-rendering)



Thus spake Michael Kiefte:

I tried running VASSAL form the command
line, but I still get the no-text problem in Twilight Struggle. My guess
is that if it works, the UseQuartz perhaps doesn’t get passed on when
the module manager launches the child process?

That is entirely possible. I’ll have to look into it.

This is correct—that flag wouldn’t be passed on to the Player by the
Module Manager in 3.1.

  1. Do we need to start the MM with that flag?
  2. Do we need to start the Player and Editor with that flat?
  3. What’s the exact syntax for the flag?

Let me know, and I’ll make the changes.


J.

  1. No
  2. Yes
  3. -Dapple.awt.graphics.UseQuartz=false

Thus spake bdgza:

“uckelman” wrote:

Thus spake Michael Kiefte:

I tried running VASSAL form the command
line, but I still get the no-text problem in Twilight Struggle. My
guess
is that if it works, the UseQuartz perhaps doesn’t get passed on
when
the module manager launches the child process?

That is entirely possible. I’ll have to look into it.

This is correct—that flag wouldn’t be passed on to the Player by the
Module Manager in 3.1.

  1. Do we need to start the MM with that flag?
  2. Do we need to start the Player and Editor with that flat?
  3. What’s the exact syntax for the flag?

Let me know, and I’ll make the changes.


J.

  1. No

On reflection, we probably should start the MM with this flag, since it
to could have SVG icons which are misrendered.

  1. Yes
  2. -Dapple.awt.graphics.UseQuartz=false

I’ve created a bug for tracking this problem:

vassalengine.org/tracker/sho … gi?id=2924

Here’s a test build for you to try:

nomic.net/~uckelman/tmp/vass … macosx.dmg

(Somebody who’s not having the problem should also try this, to verify that
the change doesn’t cause any new problems.)


J.

Just tried TS in the test build on my PPC machine, and the problem is gone. There is text on the cards.

The define we need is:

-Dapple.awt.graphics.UseQuartz=false

While this would ensure that everyone gets to read SVG text on Mac, it means
no one gets to use the Quartz pipeline in Mac. Does that matter?
Apparently Quartz has better antialiasing…

You can compare here:
nanoant.com/apple/leopards-j … -rendering

It probably doesn’t make that much difference in the long run. Shall we
build the switch into 3.1.15?

  • M.

On 5 September 2010 11:49, Joel Uckelman uckelman@nomic.net wrote:

Thus spake Michael Kiefte:

I tried running VASSAL form the command
line, but I still get the no-text problem in Twilight Struggle. My
guess
is that if it works, the UseQuartz perhaps doesn’t get passed on when
the module manager launches the child process?

That is entirely possible. I’ll have to look into it.

This is correct—that flag wouldn’t be passed on to the Player by the
Module Manager in 3.1.

  1. Do we need to start the MM with that flag?
  2. Do we need to start the Player and Editor with that flat?
  3. What’s the exact syntax for the flag?

Let me know, and I’ll make the changes.


J.

The define we need is:

-Dapple.awt.graphics.UseQuartz=false

While this would ensure that everyone gets to read SVG text on Mac, it means no one gets to use the Quartz pipeline in Mac.� Does that matter?� Apparently Quartz has better antialiasing…


You can compare here:
nanoant.com/apple/leopards-j … -rendering


It probably doesn’t make that much difference in the long run.� Shall we build the switch into 3.1.15?

- M.

On 5 September 2010 11:49, Joel Uckelman <uckelman@nomic.net> wrote:

Thus spake Michael Kiefte:
> > I tried running VASSAL form the command
> > line, but I still get the no-text problem in Twilight Struggle. My guess
> > is that if it works, the UseQuartz perhaps doesn't get passed on when
> > the module manager launches the child process?
>
>
> That is entirely possible. I'll have to look into it.
>

This is correct---that flag wouldn't be passed on to the Player by the
Module Manager in 3.1.

1. Do we need to start the MM with that flag?
2. Do we need to start the Player and Editor with that flat?
3. What's the exact syntax for the flag?

Let me know, and I'll make the changes.

--
J.

Thus spake Michael Kiefte:

The define we need is:

-Dapple.awt.graphics.UseQuartz=false

While this would ensure that everyone gets to read SVG text on Mac, it means
no one gets to use the Quartz pipeline in Mac. Does that matter?
Apparently Quartz has better antialiasing…

You can compare here:
nanoant.com/apple/leopards-j … tz-pipelin
e-font-rendering

It probably doesn’t make that much difference in the long run. Shall we
build the switch into 3.1.15?

Already got it. Since false is the default with Java 6, turning it off
won’t affect many people.

It would be nice to know what exactly the problem is, though.


J.

Already got it. Since false is the default with Java 6, turning it off
won’t affect many people.

It would be nice to know what exactly the problem is, though.

That’s Apple’s problem though. Sounds like a bad bug, however.

  • M.

Already got it. Since false is the default with Java 6, turning it off

won’t affect many people.



It would be nice to know what exactly the problem is, though.



That's Apple's problem though.� Sounds like a bad bug, however.

- M.