Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Zoom Cursor Tracking #3

Closed
infininight opened this issue Jul 8, 2014 · 6 comments
Closed

Zoom Cursor Tracking #3

infininight opened this issue Jul 8, 2014 · 6 comments
Assignees

Comments

@infininight
Copy link
Member

The Zoom accessibility feature in OS X allow text cursor tracking (so that when you are typing you don’t have to move the mouse to move the zoom window to where you’re currently typing text)

  1. Enable Zoom in System Preferences -> Accessibility -> Zoom, and ensure you have checked the box for “Zoom follows text cursor”.

  2. Load TextEdit (this is for comparison reasons, showing the expected result)
    Zoom in with either Opt+Cmd + to a point where you’re seeing only a portion of a TextEdit document.
    Type something, enough for it to go off the view, Zoom will “jump” to the current place where the text cursor is, and keeps doing so as you go onto a new line, etc.

  3. Open up a TextMate document, any code, any theme. I mainly use HTML, CSS, JS, Python, PHP and SQL.

    Create a simple script, making sure you make it longer than the zoomed in view, you’ll find that Zoom only follows part of what the text cursor does, Normally only a new line jump.

  4. Remember to go back into Accessibility in System Preferences and disable Zoom follows text cursor - otherwise you’ll have your screen jumping around and this can be disorientating for a non-Zoom user.

Opt-Cmd + (Zoom In)
Opt-Cmd - (Zoom out)
Ctrl + two finger drag up/down (dynamic zoom with trackpad)
Opt-Cmd 8 (enable/disable zoom)

Originally reported via email

@dusek
Copy link

dusek commented Jul 8, 2014

Thanks very much for the report, I'll take a look at it this or the next weekend.

@dusek
Copy link

dusek commented Jul 12, 2014

I looked at this and it looks like two separate issues:

The second one is of course more important for the user (and more mysterious for me :-)

@dusek
Copy link

dusek commented Jul 21, 2014

FYI, both dependent issues (#3 and #4) have been resolved in latest master of textmate/textmate.

@dusek
Copy link

dusek commented Aug 22, 2014

@infininight I was wondering if you got any feedback from the client about whether the issue has been resolved in latest releases and whether this issue can thus be closed?

@infininight
Copy link
Member Author

Got a reply back today, he says it works great!

@dusek
Copy link

dusek commented Sep 3, 2014

That's great to hear!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants