Andre Poenitz <[EMAIL PROTECTED]> writes:
| But's easier to build up a stack of insets at position (x,y) and go
| inside-out until the first inset shouts 'I can handle it!'.
| The effect is the same and the implementation is much simpler.
Won't you need a back pointer then? All insets must know their owners?
>> | Fine with me. Currently the canvas related part of this top dispatch is
>> | LCursor::dispatch, which can be merged with the View's dispatch if the
>> | thing is ripe.
>>
>> What do you mean by merge here? If the only change is that you get one
>> huge function that better leave them as two distinct functions.
>
| I just wanted to be nice and not rip your idea of having a 'top'
| dispatch apart...
and now you just confused me instead.
--
Lgb
