Re: PATCH: Bug 186

I want Adam's perspective on this before the discussion proceeds any
further.  After all, it is the perspective that matters. :)

-----Original Message-----
From: David Crawshaw [mailto:[email protected]]
Sent: 22 March 2003 01:35
To: [email protected]
Subject: Re: [xwt-dev] PATCH: Bug 186



On Friday, March 21, 2003, at 11:54  PM, Charles Goodwin wrote:
> You're still redirecting the box from somewhere, which is what you are
> complaining about.
>
> The only way for the box to be not-redirected is for it to be defined 
> as an
> xwt.newBox().apply() instead of as <box> somewhere.
>
> And, regardless, you can still move boxen manually by doing:
>
> $otherplace[$otherplace.numchildren] = mypreviouslydefinedbox;
>
> I suppose it comes down to you wanting to know whether a box has moved
> (presuming that if you do it yourself, you know it has moved) but if 
> the
> documentation for widgets like scrollpane is clear that they operate 
> in this
> way, then what's the issue?

I would naturally assume I can do the following:

<scrollpane>
     <box/>
     <box/>
     <box/>
</scrollpane>

It should produce a box with three boxes in a scrollpane. That's the 
naturally intuitive way for it to work. The extra north/south/etc axis 
are extra features that will be used by very few people.

If we're careful, we can make all the widgets work in almost the same 
way. Makes life easier.

> All you are doing is forcing a long way around / extra code / extra
> difficulty on the situation.  Preventing _0 from moving boxen is
> *pointless*.

Not pointless, but it is almost impossible - as far as I can tell. My 
patch only stops cascading. However, I'm not going to commit code into 
the widgets repository that redirects using _0, because it's just ruins 
the XWT Way(tm) of doing stuff.

d


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