<<< Date Index >>>     <<< Thread Index >>>

Re: For 1.5.9: menu_move_off (was: Change in behavior <current-middle>)



 On Saturday, March 26, 2005 at 4:14:12 PM +0900, Tamotsu Takahashi wrote:

> I made a new function to be used by both <next-page> and <half-down>,
> and another one for both <prev-page> and <half-up>. So, they will use
> the same algorithm.

    Fine, much thanks! :-)

    Unfortunately cursor positioning changed. Let's say you see 4-37
cursor on 30, then <previous-page>: You should see 1-34 cursor on 1. But
you see 1-34 cursor on 27, and have to <previous-page> again to set
cursor on 1.

    There are also small illogical effects in middle index, but
difficult to put in words: What I called "fixed altitude" still works,
but not always.


> On Fri, Mar 25, 2005 at 07:33:50PM +0100, Alain Bench wrote:
>> we need a menu context for page jumps setting, with 0 lines as
>> default. Or is it bloat?
> What do you mean?

    That would be with $menu_page_context=1 say 1-34 + <next-page> =
34-67, with 1 common line of context between old and new page. This can
ease user following jumps. Probably choices can be only 0 or 1 line, and
<half-{up,down}> don't need it (only for <{previous,next}-page>).

    The more I think to it the more I feel it would be usefull.


> If you type 41 when your screen is showing 9-42, you expect to see the
> same screen (9-42) ? Ignoring $menu_context is easy: see below.

    No, these numbered jumps are directed by cursor, user expects it
works as scrolls, jumps to <next-new>, searches, jumps to parent, and so
on. Cursor commands, x-y follows.

    By /page jumps/ above I meant only the 4 <{previous,next}-page> and
<half-{up,down}>. Directed by x-y, cursor follows. More or less.


>> <{top,bottom}-page> trigger menu scrolling by $menu_context lines,
>> which is surprising. Better ideas?
> I made a new redraw-flag; REDRAW_IGNORE_CONTEXT. <top-page> and
> <bottom-page> will use it to get rid of the effect of $menu_context.

    You'll say I'm never happy, but... This delays the scroll (and
surprise) to the first following cursor movement. Not good.

    I was probably more thinking to limit cursor position to top +
$menu_context or bottom - $menu_context. 50-83 cursor on 70, then
<top-page>, would give 50-83 cursor on 57. But this also is a bad idea,
especially with huge $menu_context.

    No: Let's say current behaviour is not *so* bad, please forget this
bullet was written.


Bye, and thanks again for the good work!        Alain.
-- 
How to Report Bugs Effectively
<URL:http://www.chiark.greenend.org.uk/~sgtatham/bugs.html>