Thanks, that's a relief of sorts to understand I was not missing something!
This begs the question of how best to store unit data with the functionality currently there. I'm guessing there is already a method, but being new, I have probably not found it yet. What I'm trying to do is store data for each unit type in the right click menu somewhere (there's too much data to be displayed on the piece itself) or in a pop-up text box or something like that. I don't want to create a protoype for every piece (there are well over a thousand of them) but I would like some of the values from the protoypes to be displayed. So far I've managed a kind of half way house, where I put a data sheet on every unit, with the unique data, and I find other ways to display data that cascades from the prototype (such as on the unit itself). Is this the smartest way? Ben --- In [email protected], "Rodney Kinney" <[EMAIL PROTECTED]> wrote: > > > 1) right clicking on the graphic and changing the data on the piece. > > > As was pointed out, pieces copy the data out of the prototype when they're > created, so this doesn't work. > > 2) setting up global properties for the data fields, and using markers > > on the individual game pieces to load the individual values. Problem > > is, $Format$ does not seem to work for data sheets - I get $Format$, > > not the actual value. > > > This doesn't work, but it probably ought to. I will see whether this can be > fixed in the next release. > > rk > > > [Non-text portions of this message have been removed] >
