On Thu, 2005-04-14 at 10:43 +0200, Michel Bardiaux wrote: > > With that in mind, my first question is whether this needs to be a > > new widget, or a new trait. > > > > (Make no mistake: traits may look strange, or they may appear to be hard > > stuff because of terms like multiple inheritance, but they're usually > > surprisingly easy to implement.) > > I have zero experience with traits, so tell me whether you can add a > trait to existing widgets (in this case, Core and Gadget) without > subclassing them. But note that LiteClue does *not* subclass Core nor > Gadget; it is a subclass of Shell, the hooks are explicitly installed by > an API. What OM2.2 did was intended to control the tooltips via resources.
Yes, my traits remark is based on the assumption of either adding to
XmGadget+XmPrimitive+XmManager, or subclassing them.
I understand that this doesn't solve your problem.
> Another issue is that the filtering of events away from X-insensitive
> widgets is buried rather deep in Xm and Xt. LiteClue works by having its
> own events dispatcher. So, with Lesstif or OM 2.1 or 2.2, where there is
> *no* way to make any change inside them, I'm afraid the implementation
> will never look very clean. It *exists* and I thought that rather than
> keep it for myself it would be better to put it in an opensource
> distribution.
>
> Could we please *first* add it to Xlt? Later we could see how to make it
> a trait, but IMHO that should first be a spec proposal for OM2.3
Still no reply from Rick. He should have been faster if he wanted to
object, so send me your stuff and I'll add it to Xlt.
Danny
--
Danny Backx ; danny.backx - at - scarlet.be ; http://danny.backx.info
signature.asc
Description: This is a digitally signed message part
