Pavel Sanda <[EMAIL PROTECTED]> writes:
>> needsUpdate returns true when the status of the selection has changed
>> (turned on or turned off).
>
> you meant selHandle?
Indeed.
JMarc
Jean-Marc Lasgouttes wrote:
> "Vincent van Ravesteijn - TNW" <[EMAIL PROTECTED]> writes:
> > Removing the first solves the problem and it works
> > perfectly.
> >
> > Can anyone tell me why this term is needed or did I just solve the bug ?
> > (Or I might to have to look somewhere else?)
> >
> needsUpdate returns true when the status of the selection has
> changed (turned on or turned off). While your patch is indeed
> the right solution for table movement,
Well, actually it wasn't the right solution as I realized later that the
expected behaviour is that after the first keystrok
"Vincent van Ravesteijn - TNW" <[EMAIL PROTECTED]> writes:
> Removing the first solves the problem and it works
> perfectly.
>
> Can anyone tell me why this term is needed or did I just solve the bug ?
> (Or I might to have to look somewhere else?)
>
> PS. The description of cur.selHandle(..
Hi all,
When your cursor is in an empty cell of a table and you hit
Shift+Right-Arrow, nothing happens. Hitting it again selects both cells,
which you would expect after the first keystroke. The same happens when
you are in the last position of a cell and you've not selected anything
yet.
This
