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 at
http://groups.google.com/group/google-wave-api?hl=.
