Scroll Without Moving Cursor Topic is solved

[Sweetins]

Hello all, basically am trying to scroll in MS Word like I would in a pdf.
Am trying to prevent the down or up arrow keys from moving the cursor when pressed but only scroll.
Apparently there appears to be some difference between the two hotkeys below and I don't seem to understand why.

Code: Select all

Up::Click WU

Up::
if pagelight 
Click WU
else
Send {Up}
return

The first one works fine as I expect but in this single line hotkey I can't seem to include any condition. The second one does the scrolling but also moves the cursor. First off can anyone help explain how the single line hotkey differs from the multi? And secondly how do I get my scrolling happening without cursor movement (there has to be a means of basing the hotkey on a condition.

[mikeyww]

It works but depends on the value of pagelight. Use the hook.

Code: Select all

$Up::
If pagelight
 Click WU
Else Send {Up}
SoundBeep, 1500
Return

Explained: Dollar

Maybe easier:

Code: Select all

#If pagelight
Up::Click WU
#If

[Sweetins]

It works but depends on the value of pagelight. Use the hook.

Code: Select all

$Up::
If pagelight
 Click WU
Else Send {Up}
SoundBeep, 1500
Return

Explained: Dollar

Than for the response. But same result, scrolls and moves the cursor up. And if am right the $ is to prevent the hotkey from triggering itself in case the Send command is to activate a trigger. The condition pagelight is always true so the Send doesn't even get to happen.

Maybe easier

Code: Select all

#If pagelight
Up::Click WU
#If

This might work but there already a contest sensitive condition for MS Word within which all the hotkeys are. I'd not liked to create another #If contest.

[mikeyww]

Try the posted script by itself before integrating it into your own script. You can report back on whether this script works.

By itself:

Code: Select all

pagelight := True
#If pagelight
Up::Click WU
#If

[Sweetins]

Maybe easier

Code: Select all

#If pagelight
Up::Click WU
#If

This might work but there already a contest sensitive condition for MS Word within which all the hotkeys are. I'd not liked to create another #If contest.

Yh, using the #If contest will work indeed like I did imply

[mikeyww]

If this script works alone but not inside your script, then you can post your script for feedback about it.

[Sweetins]

It works as well. Thanks a lot.

But just thinking out loud why won't this just scroll without moving the cursor Up

Code: Select all

Pagelight:=True
 Up::
 If Pagelight
 Click WU
 return

But this does it perfectly?

Code: Select all

 Up::Click WU

What is it with executing the If condition first before the Click WU makes it move the cursor as well as scroll?

[mikeyww]

That's exactly what this script does. Your script is a different script, which you have not posted.

Your bug is not "If" but is instead line 1.

Explained: Auto-execute

Unlabeled code between hotkey routines is unreachable and will never execute.

[Sweetins]

That's exactly what this script does. Your script is a different script, which you have not posted.

That's very true... having had a second look at the script and doing a clean troubleshoot (analyzing with ListLines), it turns out the problem wasn't the if statement at all but a practice I've long adopted was failing me.

Code: Select all

pagelight:= True
Up::
if pagelight 
Click WU
else
Up::Up
return

Code: Select all

pagelight:= True
Up::
if pagelight 
Click WU
else
{
	Up::Up
	}
return

The two script above were all run alone (the first, being by initial) and the second works alright. It just scrolls and doesn't move the cursor.

First of, normally if I want to make the function of a hotkey an option in an if statement as in the above two scripts, I use Up::Up instead of Send {Up}. Secondly, I know single line commands for If statements doesn't need curly braces.

If I just changed the Up::Up to Send {Up} in the first script it works fine. If I wanted to maintain Up::Up and just used curly braces around it (as in the case of the second script above), it then also works fine.

The lesson to be length is not quiet clear. Should it be a practice to always use curly braces in an if statement (whether there are single or multiline commands)? Or having been using Up::Up in most instances in my script (like in the scripts above) which tends to work perfectly than Send {Up}, it is actually not a good practice?

[boiler]

Hotkeys, hotstrings, and key remaps like Up::Up are not subject to regular if/else conditions. Do not put hotkey-type definitions inside your code flow like that. The way you put conditions on hotkeys and the like are with directives: #If and #IfWin… See the examples on those pages and study Structure of a Script.

[Sweetins]

Well noted. Thanks a lot @boiler .