Release candidate for 3.2.0-beta2

Development
1

I’ve just uploaded 3.2.0-svn8342 to the usual place:

vassalengine.org/~uckelman/builds/

If no one objects, I’d like to release this as 3.2.0-beta2 over the weekend.

2

No one complained, so I’ve released 3.2.0-beta2.

3

I am finding when opening my module I get errors that were not appearing before Beta2:

Bad Data in Module: [Layer-Sector:] - Numeric field contains a non-number followProperty[TileStatus]=

where TileStatus is a numeric [DP] used in [Layer] Follow Expression: TileStatus.

This [DP] can be placed before or after the [Layer] without changing the error.

Is there any explanation for the Layer change and a suggestion to repair it (I have this error for several components in my module)?

Thanks

Flaney

4

Opening the module in edit or play mode?
Do the errors occur when you first open the module, or when you start a new game?
Could you please include the top 20 lines or so of the errorlog?
What module is this so I can try for myself?
B.

5

Sorry for the late reply… but when I click or double-click on VASSAL-3.2.0-svn8342-windows.exe I get an endless hour-glass and the install never progresses. (I usually try to install the new builds straight away but I was unavailable for a bit - sorry for the delay.)

-Mark R.

6

Thus spake mroyer:

“uckelman” wrote:

No one complained, so I’ve released 3.2.0-beta2.

Sorry for the late reply… but when I click or double-click on
VASSAL-3.2.0-svn8342-windows.exe I get an endless hour-glass and the
install never progresses. (I usually try to install the new builds
straight away but I was unavailable for a bit - sorry for the delay.)

Are you trying to install while you have an instance of VASSAL already
running?

J.

7

Nope… no instances running - I just tried again to make sure.
Ultimately, I’ll need to terminate explorer.exe and restart it go get out of the problem.

Addendum: Actually, this time I stuck it out for, perhaps, 5 minutes or so and the install finally started. I’ll let you know how it goes.

8

So, after a while it finally finished and appears to have installed correctly.
On looking closer, I noticed that a green-bar was slowly traversing the top of my explorer window each time clicked on the VASSAL install .exe. (see attachment) I’m not sure of the significance of the green bar, but it doesn’t seem like the install gets rolling until the bar has reached the right-hand side of the explorer window. The green bar does not appear at all on earlier build install .exe’s.

-Mark R.

9

Thus spake mroyer:

“mroyer” wrote:

Addendum: Actually, this time I stuck it out for, perhaps, 5 minutes
or so and the install finally started. I’ll let you know how it goes.

So, after a while it finally finished and appears to have installed
correctly.
On looking closer, I noticed that a green-bar was slowly traversing the
top of my explorer window each time clicked on the VASSAL install .exe.
(see attachment) I’m not sure of the significance of the green bar, but
it doesn’t seem like the install gets rolling until the bar has reached
the right-hand side of the explorer window. The green bar does not
appear at all on earlier build install .exe’s.

That’s weird. I have no idea why that would be.

Does this happen with 3.2.0-beta2?

–
J.

10

The errors occur when I opened to edit before selecting File | New Game.
I do get a similar error for a pieceUnit with layers when I move it the main map. These don’t occur in build 8330.
This module is is one I am building and weighs in at 11MB.

Errorlog