At 09:14 AM 10/6/2007, you wrote:
>Ok this is easy to reproduce. Create a prototype, create a prototype
>in this prototype called Target
>
>Create a game piece: Test. Copy Target into Test. Then close the game
>piece window by clicking on "OK" (and ONLY ok, do not click on the
>prototype - Target. Then go back into the game piece. Target will not
>be there.
That's a common problem that I've run into. I've learned that
when I copy and past a trait, I highlight it, look at it's
properties, click OK to lock it in and then click OK to save the piece.
The other funky thing I've discovered is that, if you move a
trait within the trait list and then hit Cancel (because you've
changed you mind) the trait disappears. Got to be careful of that one.
>--- In [email protected], "lostinnorway2002"
><[EMAIL PROTECTED]> wrote:
> >
> > --- In [email protected], Joel Uckelman <uckelman@> wrote:
> > >
> > > Thus spake "lostinnorway2002":
> > > > I'm getting a strange bug since I upgraded to 3.0.10:
> > > >
> > > > I'll copy either a whole prototype or a part of a prototype.
>Then I'll
> > > > enter the commands I want. Then when I save and go back to it, this
> > > > prototype is gone. Often it'll null pointer out and I have to shut
> > > > down the program.
> > > >
> > > > Definitely starting to get annoying. Anyone else notice this?
> > > >
> > >
> > > From what version did you upgrade?
> > >
> > > That doesn't happen for me when I try to do what you described. Could
> > > you send me the module?
> > >
> > > --
> > > J.
> > >
> >
> > I'll try to get it isolated and reproduced and send it to you with
> > instructions to replicate :)
> >
>
>
>
>
>
>Yahoo! Groups Links
>
>
>
