AutoHotkey Community

Read up on if statements here: http://www.autohotkey.com/docs/commands ... ession.htm The example section shows a similar example to what you're trying to do.

The main issue you have wrong is that your "or" clauses are not full expressions... something like: "If I have $1 or if $10". --"If 10" what? You need: "If I have $1 or if I have $10"



Not sure I understand what you're asking. But it sounds like you're introducing state http://en.wikipedia.org/wiki/State_%28c ... science%29 which is known to confusing when applying to user interfaces, particularly without indication--one of the reasons I added the change mouse cursor.

Feel free to play with these ideas though.

Thanks for the tip, the following code works great AHK didn't seem to like '|' in place of 'or', plus, as you stated the possessor needed to be stated case-by-case.


I have no coding experience, but if by state you mean I'm attempting to introduce an alternative mode of operation, then yes I'd be introducing state.  I want to replace 'Slow Mode' with a 'Scroll by Page' mode, as opposed to scrolling by lines. I'll see if i can't solve this one in my first crack at complex coding.

Thanks again cheek.

How about:

then in Scroll():


I personally did not like this at all, but you may find it works better for your use.

Exactly what i was hoping to do.  You come through again , it would have taken me forever to figure out how to code this.

It's great for longer PDF or WORD documents (not to mention image browsers & folders with a long file list), especially if you have the mouse pointer set to a low sensitivity w/ a bit of acceleration.  Page Mode will switch through tabs in Firefox also, though I wouldn't recommend using it that way (I prefer the new L/R flick gestures for that).

You could add filtering for the process name to exclude firefox.exe fairly easily; Switching through firefox tabs was my biggest issue with that setup. I like the idea of GestureL and GestureR for switching tabs, but I just set that to browser back and forward with the following code: (this will probably be in the next release)

Here's what my user-customizable handlers look like (included tooltips like you're example):
_______________________________________________________________________
A couple of things that will need cleaning up in future versions of DtS, depending on what you decide to include.  (1) With UseDoubleClickCheck=True, multiple flick gestures performed within the double-click threshold change the mode of operation.  (2) Flick gestures and page mode scrolling are sent to the window with current keyboard focus instead of activating directly beneath the pointer.  (3) \/ see below \/

If 'page mode' becomes official there will definitely need to be a permanent visual cue, a tooltip isn't enough indication.
_______________________________________________________________________
UPDATE:  quick fixes to activate windows for 'flicking' and 'page scrolls'.  probably not the cleanest way, but it works.

awesome script.

This may be a stretch, but I added the following scripts into the FireGestures extension as L/R gestures;

Rewind (Go to First Page of History)

Fast Foward (Go to Last Page of History)
would it be possible for an AHK script ( DragToScroll ) to send these commands to the Firefox browser, or do they need to be sent from within the browsers framework (i.e. an extension).

Do you have to choose "Watch this topic" every time you reply for it to keep emailing you? It doesn't like to.... Sheesh.

Thanks for this; its something to be aware of, I don't think there's a technical bug here, but the settings may need to be tweaked. We've got a lot of functionally assigned to a single button, and it starts to become difficult for this functionality not to overlap. Maybe try simply lowering the doubleclick threshold.

This is because of your handlers for GestureU/L using 'Send.' This autohotkey command is only able to send keystrokes to the active window, which is also the reason why the WheelKey method (simply 'Send {WheelUp}') cannot scroll background windows. Your solution to simply activate it is what I would have done.

The code you posted has the ability to interact/read the browser history, which ahk cannot do (not that I know of anyway), so it will not know how far back to go to get to the first entry. AHK can simply 'Send, {Browser_Back}' to go back a single entry in the history. Again, this will only work when the browser is active. You could also send this command multiple times, but you wont know how many you need... maybe sending "a lot" would be sufficient??


Thanks! Enjoy

Does anyone know if there's something like this for Mac? I know the touchpad and magic mouse have the two finger scrolling, but I often use a regular USB mouse and I cant break the right-click-drag habit. I keep selecting things from the context menu.... Doh.

lol, I always get e-mail updates on watched topics, even after several months. Maybe you haven't selected the following option in your profile "Always notify me of replies:"

Indeed, there is a lot assigned to the active button (MButton for me). I've already lowered the multi-click threshold in mouse properties as far as I can while keeping the ability to triple-click . I usually end up changing modes while trying to rapidly go back a couple pages/folders in a browsers history.

Speaking of doing too much with MButton . I inserted the following code at the end of DtS. Unfortunately ended up having to line out commands that begin with MButton so as to not break DtS.


I thought that one would be a stretch

Here you go cheek, Smart Scroll, not free though
OSX also appears to have grab-scrolling built in http://www.usingmac.com/2009/8/4/daily-trick-21
Another, MaxiMice, not free
Yet another, Scrollabillity, not free

I've never used a MAC (well not for 20+yrs), so can't vouch for any of these.

Just a note from a random user -- Thanks for a great tool!

I don't know if you're aware of this -> IronAHK (alpha): cross platform .NET rewrite of AutoHotkey.

Maybe you could use it to port your script over to OS X.

This is a great MouseImp replacement that works on Chrome with nice iPhone-like momentum feature.

If I can throw a few suggestions that are humbly 'in my opinion':

1) When drag-scrolling inside a broswer that includes scrollable text windows, don't scroll the text of the text windows unless the right-click point of origin is already inside the window. This allows the user to scroll all the way to the bottom without unintended sub-scrolls.

2) Make the scrolling smoother (finer increments) like MouseImp.

3) Change the icon to a closed/grasping hand when drag-scrolling.

4) Include instructions in your Readme documentation for non-techies that want to start Windows with the hotkey.

Thanks drewwesley, gleeby; glad folks are still finding this I submitted this to Lifehacker a few times, but haven't seen a post about it. Thanks to MainTrane for submitting it to the MouseImp site. Feel free to submit this to any relevant blogs or sites; I'd love for it to explode

I pushed out a new version today 2.4, that is primarily a bug- and compatibility-fixes release.

This update fixes a minor bug for all apps which do not report control id's, instead sending the scrolling to the parent window, rather than the specific control. There is also a new setting that forces this behavior. This fixes scrolling for Firefox4, Visual Studio 2010, and I suspect may also help in Java apps, and some of the other previously reported apps. Try using WheelMessage in these apps, if you've previously switched to the WheelKey method.

Also included are Browser Back/Forward gestures, and a tweak to the AllSettings gui to show non-default values. Unfortunately I could not get this behavior on the various controls in AppSettings.

Download the new version from the first post. See the included ReadMe for more info on this version.

In reply to some of the recent comments & suggestions:
DtS depends on windows messaging for the default "WheelMessage" mode (WM_MOUSEWHEEL), so a port to another system is unlikely. See more below for a bit more about how DtS works.

3) should already exist in the current version. Take a look at the tray icon to see the open/close behavior in action as you're dragging. 4) is done in this release. Thanks!

Unfortunately neither of these are something I can control in this script, due the the way it is designed. See my post below for more.