erm im not quite follwing you here. what im doing is mouse wheel scrolling and having the cursor not remain within the view port. when i then hit cursor down the view port migrates away from where i specifically located it back to where the cursor is. What i would like to happen would be that when i mouse wheel down that the cursor remain within the view port. if i have mouse wheeled down 5 pages and hit cursor down to position the cursor on the piece of code im LOOKING at... i dont want the view port to suddenly automatically home itself to the cursor - if the cursor was always within the view port it would not have to do so.
Also, im not comfortouble with creating some sort of plugin to achieve this as I dont program python or know the ST3 api enough to do it. Im also working 80 hour weeks for the past 6 weeks and will probably continue to do so for the forseeable future or beyond.
This seems to me like the sort of thing that should be built in as a configurable switch, not some geeky plugin that only a ST3 geek would know how to use
I did create a syntax highlight module for my forth programming but that was all just regular expressions... none of that API stuff or python coding.
Also, the plugin code you pasted seems to be a "hit this magic keypress and the cursor will home itself to the viewport". This would not work for me, i need the cursor to ALWAYS be within the view port. IF this magic keypress would mentally work for me then all i would have to do is remember to MOUSE CLICK after doing a mouse scroll and before I hit any cursor keys.
Problem is, my 30+ years of coding has hard wired my brain into expecting the cursor to never go outside the view. Im too old and wrinkly to recode my thought patterns into doing this