Ah, I see what’s happening now. I’ve got the wizard turned off in Preferences, so when I open a new module, it never prompts.
I would suggest when a user opens an entirely new module, it overrides the “No Wizard” preference and prompts for a username/password; Otherwise it’s way too easy to kick off games with the default user/password set.
I guess the ideal solution is to let the user configure the default username/password when they install Vassal, but that can wait for a later release.
Welcome aboard Robert! What about this, it fades in… then it fades some of the way out so we’re left with a kind of shaded and less obtrusive version of the Splash.
By the way… It’s David. Only time I was called ROBERT was at school and in the army
For now I’m experimenting with the Eclipse debugger to try to see what happens with the turn tracker and I admit I’m a bit lost there. But I managed to get Eclipse to run in debug mode and I’m fiddling around with breakpoints. Many things in my EuF2 module depends upon the TurnTracker working properly so for now I’m a bit stuck. But this was completely out of topic. Sorry.
About the splash screen fading in and the fading out to a translucent background, I would say it’s even better!
We still need to get this working before releasing a beta, or its
going to give testers problems.
In 3.0 I see that the username and password are stored per module. Is
there a good reason for this, as opposed to storing a single username
and password? It would be simpler if the username and password were
global for each user, because then we could prompt the user for these
the first time VASSAL is run.
It means it’s easier to keep track of multiple aliases if you want to be a shifty, anonymous player! But seriously no, I can’t think of a good reason, but Rodney may know more about the history of why it’s done the way it is.
–
Michael Kiefte, Ph.D.
Associate Professor
School of Human Communication Disorders
Dalhousie University
Halifax, Nova Scotia, Canada
tel: +1 902 494 5150
fax: +1 902 494 5151
The hex numbering code is immensely complex to cope with sideways mode, odd column offsets and reversed numbering on each axis. It took me forever to get this stuff right. From memory, the hex ‘width’ specifies the distance between two edges, and the Size is the distance accross the hex, so this code is probably correct.
What exactly is the problem you are having? I might be able to point you in the right direction.
I’ve built a username/password dialog which should pop up in lieu of the
wizard, which you can find in svn3125
(nomic.net/~uckelman/tmp/vassal). I haven’t committed this to
the trunk yet, because it disables the welcome wizard entirely and, while
I would like to do that, I’m not certain that we have agreement on that
point.
Why is this happening? Is it because there’s not one defined in the module,
or because there is one but it’s broken in some way?
It doesn’t seem to be happening in 3.0.17 Joel; Looks like something may have changed somewhere since then. Civil War does it as does OCS-Tunisia v3.3.
AboutScreen has always been a required component. Some modules have a
null image for AboutScreen, which defeats the purpose of it, and leaves
a dead item in the Help menu.
I suppose that a better solution would be not to build AboutScreens
without images.