Re: [Clip] Selecting a word
I tried you clip, it worked fine with or witheout the Keyboard command.
With the Keyboard command the clip jumps to the next word and selects it, without the keyboard command, it selects the word to the right of the cursor.
Whenever I experience mysteries (on a regular basis) as you described, I restart NoteTab, and if that doesn't work, I reinstall it.
I should point out that I put my PC to sleep rather than shutdown, and wake it up instead of booting. This does tend to generate glitches over many sleeping sessions - sometimes I don't reboot for a week or more.
--- In firstname.lastname@example.org, Jean-François Colas <jfcolas@...> wrote:
> Le 18/01/2012 20:16, Axel Berger a écrit :
> > Jean-François Colas wrote:
> >> except when my cursor is in the first character of the word,
> >> what would be in most case (but not everytime)...
> > I don't quite understand the question, as the normal cursor (not the
> > overwrite one) never is on a character but always between characters.
> So I meant before.
> This is a mystery. Here is a clip which works at home with ntp 6.2:
> ^!Keyboard Ctrl+Right &200
> ^!Select Word
> ^!Continue ^$GetSelection$
> I play with the line:
> one two three four five
> If I start from inside "one", the word "two" is returned as the result
> of ^$GetSelection$.
> But here with NTL 6.2, the same code with the same test line results in
> nothing returned...
> If I comment the line ^!Keyboard Ctrl+Right &200, then the word is
> selected in every case except when the cursur is just before the first
> character. The preceeding word is also returned when the cursor is just
> after the word, this point I don't know if it is the normal situation.
> As if there was a sort of shift of one position
> Exception : when I press Home before executing the script (without the
> ^!Keyboard statement), the word "one" is returned.
> At Home I'm under Win XP Home, at work I'm under Win XP Pro.
> So, unless there is a difference about that between NTP and NTL, I'm
> afraid this could be a hardware problem...