On Wed, Nov 19, 2003 at 12:11:13AM +0100, Alfredo Braunstein wrote:
> - target_x handling
> - cursorUp/Down entering/exiting insets (LFUN_FINISHED_UP/DOWN where not
> handled correctly)
> - pageUp/Down (take the userguide, press page down: scrolling gets stuck at
> some point)
>
>
> There's still the eternal problem with with full-row insets: if you have a
> line like this
>
> blah blah blah
> BUTTON
> ---------------------- - - - - - -
> |here is some text
> ----------------------- - - - - -
Also
blah blah blah blah blah [I] blah blah blah blah blah blah blah blah
blah blah blah BOX blah blah blah blah blah blah
bu bu bub bu bu bu
bu bu bu b ub bub
blah blah blah blah blah blah blah blah blah blah blah blah blah blah
blah blah blah blah blah blah blah blah blah blah
is not really satisfactory. But it wasn't different befroe, so I'd just
apply this (possibly with separate xo_ and yo_ variables instead of pos?
I'd do that...)
> So say you are with the cursor in the last 't' of 'text', then you go up and
> the cursor goes to before the B of BUTTON with x_target set appropriately
> to the x coordinate of the 't'. If you try to go further up, the algorithm
> tries to place the cursor at the end of the last blah, and so goes again to
> the same position, i.e. we are stuck.
>
> Solution: we have to distinguish between the two positions, IMO.
That's the kind of fine-tuning I'd leave for the end.
Andre'
