I'm not entirely sure what you mean by "inheriting from a previous class." Are you saying that there was an old Blip class for the Java API that didn't have parent info?
I don't think it's an issue with an object just being modified to create a pseudo-new object, because one can have blip1 and then assign blip2 to be blip1.getParent() and it will work just fine. Just don't try to get the parent of blip2, as that is null. On the issue tracker, cmdskp said this lack of functionality was purposeful, and that one is not supposed to be able to access every blip in a wave on an event that returns a blip. I questioned the reasoning behind this, but he has not responded yet. Issue Tracker #468: http://code.google.com/p/google-wave-resources/issues/detail?id=468 I really don't know, and I'm quite curious as to what is supposed to be happening, but I've gotten no word from Google about it, so here I wait. On Nov 18, 10:19 pm, Vikram Dhillon <[email protected]> wrote: > Hi, > To me this seems like there are some inheritance issues going on. "This > stops with currentBlip being exactly 1 parent above bottomBlip. Every time." > This is why I think its inheriting from a previous class or some properties of > the object are being altered. Correct me if I am wrong. > > -- > Regards, > Vikram Dhillon > On Tuesday 17 November 2009 12:41:30 am Olreich wrote: > > > > > The Java API has the Blip.getParent() function. When this is called, > > the returned blip does not have the ability to "getParent()" again it > > seems. or, at the least, one cannot continue walking without hitting > > null on the second trial. The same rings true when using > > "isParentAvailable()" to check for parents. > > > Here is an excerpt of the code for walking up the blip chain. > > > Blip currentBlip = bottomBlip; > > Blip lastBlip = null; > > while ((currentBlip = currentBlip.getParent()) != null) { > > lastBlip = currentBlip; > > } > > > This stops with currentBlip being exactly 1 parent above bottomBlip. > > Every time. > > > Sample Blip chain information: > > > 12:21 > > Blip Id: b+2ew83hhsK > > Parent Blip Id:b+9k9iVrZkEzM > > Parent Available: true > > > 12:21 am > > Blip Id: b+2ew83hhsM > > Parent Blip Id:b+2ew83hhsL > > Parent Available: true > > > 12:22 am > > Blip Id: b+2ew83hhsN > > Parent Blip Id:b+2ew83hhsM > > Parent Available: true > > > 12:22 am > > Blip Id: b+9k9iVrZkE0z > > Parent Blip Id:b+2ew83hhsN > > Parent Available: true > > > 12:22am > > Blip Id: b+2ew83hhsO > > Parent Blip Id:b+9k9iVrZkE0z > > Parent Available: true > > > Using a bundle.getBlip(waveId, waveletId, parentBlipId) command to > > travel also does not work, as it stops once more at the blip just > > above. > > > What appears to be happening is that each blip, upon a BLIP_SUBMITTED > > event, has the ability to see it's parents and such, but when a blip > > is found via any of the methods of "get" there is no parent > > information on them. It would be most useful to have this worked out, > > as then it would give us at least 1 way to reliably count blips, do > > batch operations to blips, and a couple other fun things. > > > -- > > > You received this message because you are subscribed to the Google Groups > > "Google Wave API" group. To post to this group, send email to > > [email protected]. To unsubscribe from this group, send > > email to [email protected]. For more options, > > visit this group athttp://groups.google.com/group/google-wave-api?hl=. > > signature.asc > < 1KViewDownload -- You received this message because you are subscribed to the Google Groups "Google Wave API" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=.
