[messages] Edit: Re: [Developers] Cleaning out the tiles directory
mroyer1 at comcast.net
Mon Nov 19 15:36:59 MST 2012
[This message has been edited.]
The only other thing I can think of is if there were a "last played"
date property of a module that got updated when the module is played.
Tiles could expire after some long time since a last playing (whether
hardcoded or user-preference settable). But, quite frankly, I'm not
sure the issue is worth the effort especially where it's a v3.2 issue
only. When I first reported it, I didn't realize I was running into a
corner-case of design intent.
> There won't be any need for writing tiles to disk for V4---at least
> for the reference C++ client. (In the C++ demo, decoding even very
> images and slicing them into tiles in memory never takes more than two
> or three seconds; writing them to disk would be a waste of time.) So
> this is only an issue for 3.2.
Has anyone tried this with my module? I'm going to go out on a limb and
speculate that the module probably has the largest map images of any
VASSAL module to date, so it would be a good stress test for V4
in-memory tiling. The module is unreleased, but if anyone wants to test
how it "slices" in v4 I can make it available.
Read this topic online here:
More information about the messages