At 02:43 PM 5/12/2001 -0500, Ian Bicking wrote:
>Here's pertinant parts of the Classes.csv file:
>,pieces,list of Piece,0,,,,
>The important part is that Pieces are contained in Portfolios, but
>each Portfolio has a representative Piece (which will be used for the
>Portfolio's icon). I feel like MK is inferring the relation between
>the objects incorrectly in this case -- there just isn't enough
>information in this description for MK to figure out what's going on,
>really. I'm getting a weird bug as a result, which in itself probably
>isn't interesting or helpful. So how should I deal with this? Should
>I have representativePiece be an int, and do the lookup myself?
This will be fixed in general when I (or Geoff) rehash MK's list policies
In the current MK, Piece.portfolio is seen as a back reference to Portfolio
for the purposes of the pieces list. If you don't need a back ref from the
representativePiece to the Portfolio that owns it, then you can create
those rep pieces without a Portfolio ref and everything should be fine.
Does that get you by for now?