> It seems to me that we could have a fool-proof saved game updater if we
> gave every piece type a unique id, and every token of a type a reference
> to that id.
The problem is that it's usually the types that change when a module is
updated. For every piece in the old saved game, chances are there's no
longer any piece in the palette with the corresponding type. That's why the
updater goes by name.
rk
[Non-text portions of this message have been removed]
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/vassalengine/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/vassalengine/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
