> I'm genuinely curious, though, as to why that's an *important* difference in > behavior for you. > I can't think of a situation where either of those two approaches is > significantly worse or better. > What is the case you have where it makes a significant difference? Here a few cases that might illustrate why I think it is important:
- Right now pressing fn-Opt-UpArrow and then fn-Opt-DownArrow does not return cursor to the same place (or at least near it). If you think about it almost all navigation command that change cursor position have counter part that allow you to get back if you need it. But current implementation of fn-Opt-UpArrow/DownArrow does not do that. This is because amount of space it jump is different for first and second use: when we press it first time we jump less then one page (some time as little as one line) and second press will jump one page up or down. - And another reason is the cursor position on screen which we will get after using current implementation of fn-Opt-UpArrow/DownArrorw. Right now we will get top line or bottom line of the screen respectfully and this is not a good place for cursor to be. Just think about it: when we editing we almost always want to see context of editing area - a few lines above and below the cursor. But having cursor on ether very top or very bottom line effectively hide half of the context. So to see what is around you have to scroll text a bit and that an extra action which could be totally be avoided by standard implementation of this functionality. In other words after using current implementation of fn-Opt-UpArrow/DownArrow user will *almost certainly* have to reposition cursor before s/he can start editing. Erni. On Mar 27, 2:28 pm, Watts Martin <[email protected]> wrote: > On Tuesday, March 27, 2012 at 10:06 , Erni Wogernom wrote: > > - I don't mind using different key combination - that totally fine, > > the problem is that this one does not work exactly right. As I > > explained that previously - it does not keep screen position of cursor > > and that make it kind of useless. > > Ah! I see the difference you're talking about now, yes. In the case of > TextEdit, the cursor might stay on the line that's three-quarters of the way > down the screen as you page back and forth; in the case of BBEdit, the cursor > would move to the top or the bottom of the screen as you page. > > I'm genuinely curious, though, as to why that's an *important* difference in > behavior for you. I can't think of a situation where either of those two > approaches is significantly worse or better. What is the case you have where > it makes a significant difference? -- You received this message because you are subscribed to the "BBEdit Talk" discussion group on Google Groups. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at <http://groups.google.com/group/bbedit?hl=en> If you have a feature request or would like to report a problem, please email "[email protected]" rather than posting to the group. Follow @bbedit on Twitter: <http://www.twitter.com/bbedit>
