RE: pfLoad of DWB
Tanaka, Ken (Ken.Tanaka++at++williams.af.mil)
Thu, 11 Feb 1999 09:15:08 -0700
> -----Original Message-----
> From: Les Elkins [SMTP:lelkins++at++lnk.com]
> Sent: Thursday, February 11, 1999 7:52 AM
> To: info-performer++at++sgi.com
> Subject: RE: pfLoad of DWB
>
> Don't know if it's your problem, but...
>
> I seem to recall that pfPrint uses forward slashes to display the
> complete paths of the nodes it is visiting. As it is traversing the
> graph, when it backs up a level, it pops the text off the end of the
> printed path by backing up to the last forward slash in the path. If
> any named nodes in the DWB database have forward slashes, they will
> cause the path printed by pfPrint to gradually get more and more
> confused as it traverses the graph.
>
That seems to be exactly what's happening--there is a slash between every
node name and the entire history of the traversal is building up in the path
text. The nodes themselves don't have slashes but pfPrint seems to be
either tacking on too much of the path (at least some of the time) for child
descents or not popping off enough of the path when re-ascending to a
parent.
By experimentation I've noticed that DWB allows just about any text in the
node names, including spaces, slashes, quote marks and other punctuation.
Only the spaces are being used in my model--perhaps they are messing up path
algorithm.
I'm not working on cleaning up the pfPrint though, since it's mostly doing
what I need.
-Ken
This archive was generated by hypermail 2.0b2
on Thu Feb 11 1999 - 08:15:15 PST