Yeah, I just tried it again and still no-go. I’m still using build 7857 if that matters.
-Mark R.
Yeah, I just tried it again and still no-go. I’m still using build 7857 if that matters.
-Mark R.
I just d/l and tried latest build 7874 and couldn’t connect with it either.
Thus spake Tim M:
Side topic - Ive spotted a few backward compatibility issues in MM,
remind me to bring those up after this is solved!
What are these?
–
J.
Can you confirm whether this is fixed with the latest build?
This now works as you describe in 7874
-----Original Message-----
From: messages-bounces@vassalengine.org
[mailto:messages-bounces@vassalengine.org] On Behalf Of Joel Uckelman
Sent: Tuesday, October 04, 2011 3:53 PM
To: messages@vassalengine.org
Subject: Re: [messages] [Developers] Re: 3.2 builds
Thus spake Tim M:
build 7809
The tiling/caching pre processing of module images only works on base
module. It does not pick up any images found in module extensions that
are loading. This causes a lot of …011-09-12 11:07:03,389 [3-AWT-EventQueue-0] WARN
VASSAL.tools.ErrorDialog - Image not found:
24dd6351be204abaf61bb8abcbf61b3080511eeb
2011-09-12 11:07:03,389 [3-AWT-EventQueue-0] WARN
VASSAL.tools.ErrorDialog - Image not found:
becbd125990949fdc340d79413c792b030f02b4f…and so on
No map board shows if the map was in the extension naturally (or any
other image from extension of course). That is going to be a problem
Try svn7874. As it is now, each extension will end up with its own
slicing process and progress dialog, which is kind of stupid. I’m mainly
interested in whether this works at all at present.
–
J.
If you use an older version of Vassal than the one a module was created in,
it still will allow you to add an extension even though the module is
“grayed out” for editing purposes.
I think the “New Extension” / “Add Extension” menu selections should also be
disabled in this case just like “Open Module” and “Edit Module”
The other thing I saw isn’t popping out as obvious right now - I’ve slept
since I last looked ![]()
-----Original Message-----
From: messages-bounces@vassalengine.org
[mailto:messages-bounces@vassalengine.org] On Behalf Of Joel Uckelman
Sent: Wednesday, October 05, 2011 5:10 PM
To: messages@vassalengine.org
Subject: Re: [messages] [Developers] Re: 3.2 builds
Thus spake Tim M:
Side topic - Ive spotted a few backward compatibility issues in MM,
remind me to bring those up after this is solved!
What are these?
–
J.
Thus spake soft-bug:
The previous colored icons (editor mode) were blue/grey in the 3.1
series were neutral… now the yellow ones focus your attention on them
Which icons do you mean? Could you post a screenshot of them?
–
J.
Thus spake Joel Uckelman:
Thus spake soft-bug:
The previous colored icons (editor mode) were blue/grey in the 3.1
series were neutral… now the yellow ones focus your attention on themWhich icons do you mean? Could you post a screenshot of them?
Never mind, I see from the screenshot here:
–
J.
It’s worse on Vista where a different Icon is used:
Thus spake Brent Easton:
It’s worse on Vista where a different Icon is used:
Are those the standard tree icons in Vista?
–
J.
Yes
Thus spake Brent Easton:
Yes
Since those are the standard tree icons, are they really a problem?
–
J.
Here’s a Vista tree view from windows Explorer for comparison. Obviously different. Main problem is the JTree Row height.
Just tried the newly created build svn7883 and this issue is fixed. I can connect to the server.
Thanks,
-Mark R.
I’m working with svn7898, and I’m getting a bunch of ‘image missing’ messages in the F&E module. This is odd, since I’m pretty sure that every image I’ve ever done has had a lower case extension since day one. Here’s a very partial list of complaints:
Those look to mostly be older images, so it might have to do with how Vassal was storing data once upon a time. (I do not remember what version of Vassal this module started with, but it’s been many moons.)
Thus spake Rindis:
I’m working with svn7898, and I’m getting a bunch of ‘image missing’
messages in the F&E module. This is odd, since I’m pretty sure that
every image I’ve ever done has had a lower case extension since day one.
Here’s a very partial list of complaints:
I’ll bet these images are GIFs whose filenames were stored in the saved
games without their ‘.gif’ extensions. If so, I know what the fix is,
but I haven’t had time to implement it yet.
–
J.
I’m getting the errors when starting a new game, while flipping through the counter selection menus. So, if you really mean a *.vsav file by your mention of ‘saved games’, no that’s not it.
Thus spake Rindis:
I’m getting the errors when starting a new game, while flipping through
the counter selection menus. So, if you really mean a *.vsav file by
your mention of ‘saved games’, no that’s not it.
Then it’s in the module, but still the same problem.
–
J.
Thus spake Joel Uckelman:
Thus spake Rindis:
I’m getting the errors when starting a new game, while flipping through
the counter selection menus. So, if you really mean a *.vsav file by
your mention of ‘saved games’, no that’s not it.Then it’s in the module, but still the same problem.
I reintroduced the check for extensionless GIFs. (Blech!) Try the
svn7915 build.
–
J.
That did it.
I checked inside the module, and as I expected, every image has an extension. So the problem should be in the buildfile. I don’t suppose you could just quietly check and re-save build files of modules the first time Vassal 3.2 opens them? 