Re: Bug in pfflt

New Message Reply Date view Thread view Subject view Author view

Marcus (Marcus++at++multigenuunet.UU.NET)
Fri, 23 Sep 1994 10:19:50 PST

        Reply to: RE>Bug in pfflt
>From: watsen++at++netcom.com (Kent Watsen)
>Message-Id: <199409200245.TAA17857++at++netcom.netcom.com>
>Subject: Bug in pfflt
>To: info-performer++at++sgi.com (performer)
>Date: Mon, 19 Sep 1994 19:45:39 -0700 (PDT)
>
>I've discovered that the cleanTree routine employed
>by LoadFlt does not retain NodeNames. Although one
>may register a CB_CLEANNODE callback, there is no
>way to set the new node's name without extensive
>programming. The line of code in line 2196 of hier.c
>fixes this error: pfNodeName (cnode, pfGetNodeName(child));
>
>Kent Watsen
>DCS Corporation
>Simulation Branch
>703.683.8430 x369

But Kent, cleanTree() does not create new nodes. It recursively:
[1] removes groups that have no children and
[2] collapses singleton group hierarchies (paths) from the bottom.
Apparently you find it useful, in case [2], to transfer the name of
the group being deleted into its (former and only) child.
Hmm ... so you're trying to preserve some set path? What about
the child's original name? It may have been important too?

Renaming like this could occur repeatly during the process,
leaving the ultimate child (say a pfDCS) with the name of the
top most group that was removed. What if said pfDCS's name
was important too?

I understand the need to track the nodes that cleanTree() is
removing from the hierarchy. My intention is to provide a
better loader callback facility that gives the user various
veto powers and node (subtree) substitution.

Regards,
Marcus Barnes, Member Technical Staff
MultiGen Inc., 1884 The Alameda, San Jose CA, 95126
PH: (408) 261 4118 FX: (408) 247 4329
EMAIL: multigen!marcus++at++uunet.UU.NET

New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:50:33 PDT

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.