Re: child wrappers

That's a very contradictory reply.

The whole point of redirect wrappers, I thought, was to keep 'access'
xwt-like, ie if group has a redirect that wraps:

<group id="g">
    <box id="0" />
    <box id="1" />
    <box id="2" />
    <box id="3" />
</group>

$0 == g[0]
$1 == g[1]
$2 == g[2]
$3 == g[3]

But what you just said would mean:

$0 != g[0] but rather $0 == g[0][0]
$0 != g[1] but rather $1 == g[1][0]
etc

And considering your stance on my scrollpane redirects, this is... er... a
confusing stance for you to take.

Unless of course I'm mistaking what you mean by read traps... as in, use the
read traps to redirect to the wrapper?  (As opposed to use read traps to
redirect to the child.)

-----Original Message-----
From: David Crawshaw [mailto:[email protected]]
Sent: 09 April 2003 12:11
To: [email protected]
Subject: Re: [xwt-dev] child wrappers



On Wednesday, April 9, 2003, at 09:14  PM, Charles Goodwin wrote:
> If you want all properties other than 1 or 2 to be ignored by the 
> wrapper.
> How will this be handled, a 'listen' list?  (I only ask because it was
> omitted from the example.)

You'd put read traps on the specific attributes.

This wrapper system isn't really designed to redirect attributes, but 
to provide seamless graphical support for the children (ie the tree 
widget). It's to avoid many of those situations where the easiest 
solution is to move a child from _0.

d


_______________________________________________
http://lists.xwt.org/listinfo/dev
_______________________________________________
http://lists.xwt.org/listinfo/dev