Thus spake "Bill Thomson": > Where do i find a listing of attributes of the progression of 3.0.x? > is there a version history posted somewhere?
There's not a version history posted anywhere at present. We should be keeping one someplace. For 3.0.x, If there were one, it would be of limited value, however, as I wouldn't recommend that anyone use any version of 3.0.x other than the most recent one. > Whatever value is attributed, functionality of many of my modules is > lost due to noncompatabilty of custom code, all hot keys lost, etc. I > have directed scores of people in tournament/ladder play to use 299 for > these modules. Vassal evolves continuously, perhaps for a new venue > but sacrificing the original boardgame application. We need you to give us a detailed list of what has stopped working; otherwise we can't look into any of it. Some might be very simple to resolve within the modules. Some might be caused by bugs we introduced from 2.9.9 to 3.0.x. Without the specifics, we'll never know. > I could reestablish my java education to so can continuously update a > score of modules to maintain capability to keep up with engine > changes. Same value vs effort question. The primary component for which there's an incompatibility between 2.9.9 and 3.0.x is the turn tracker. We should have written something to update modules which use that automatically. We still could---it's Brent's code, so he'd be best suited for that. Maybe he can comment. As for other custom components, it's the same story as above: Maybe they should still work, maybe they require minor changes, but we'll never know unless you make us aware of what exactly doesn't work in which modules. -- J.
