(Question for Brent: I’d like to name and locate the VASSAL app icons in
the way that we’re going to handle icons in 3.2 so that we don’t have to
move and rename them. Unfortunately, I need some pre-rendered sizes for
the app icons which Tango doesn’t use, e.g., 48x48, 64x64, 128x128, and
256x256 and so those might not fit in well with our new scheme. Comments?)
The Icon is there - looks a bit funky. The “V” seems proportionatly
incorrect or its attempting to look 3d but its not coming through in this
sense
My desktop icons are set to 48px rgb perhaps reason why
For pre rendering you only need the base Tango Icon image, then just use
something like Axialis IconWorkshop to create all your different sizes from
it to get a full range set
My first attempt to run this is failing. I am getting a dialog claiming that an instance of Vassal is already running. Am getting this with the older installers also. I haven no instance of Vassal running. What is it checking? Looks like I need to do a reboot to get it going…
48x48 is one of the stamdard Tango sizes (Large).
The work I have done can easily be scaled to included your other sizes (64x64, 128x128, and 256x256), so I don’t see any problem if we just extend the sizes we support.
Icons work with saved games and mods but not extensions (vmdx)
Probably early for this now but the three types should probably differ
slightly somewhat to be easily recognizeable instead of all being identical
While we can launch modules directly from the vmod or vsav, it is not
possible with the vmdx and if the user has their file extensions turned off
(which is default in winblows) and does not know how to turn on, they are
not going to be able to tell what type of file they are trying to start
The installer uses a mutex to make sure that only a single instance runs.
Possibly the mutex wasn’t unlocked after the last time you ran the installer
successfully—but that would be a Windows or NSIS problem, not a problem
with our installer, as the mutex is supposed to be unlocked automatically
when the process locking it ends. (It’s also possible that you have a zombie
installer process running, which is still holding the lock.)
There’s a good reason for providing pre-rasterized app icons for large sizes,
namely that the app icons are needed at start-up and rasterizing them at
start-up means that we have to load all of Batik at start-up—that would be
nice to avoid.
Is it worth extending size support to add several sizes where our app icon
will be the sole icon at that size?
It is virtually zero work for me to add the additional sizes and performance will not be affected, so I don’t see why not. They are a good range of sizes that we may well find useful for other purposes later.