bugGNU Octave - Bugs: bug #39731, Scroll only if the current scroll...

 
 

bug #39731: Scroll only if the current scroll bar slider is near the bottom of the history window.

Submitter:  Dan Sebald <sebald>
Submitted:  Thu 08 Aug 2013 05:01:42 PM UTC
   
 
Category:  GUI Severity:  3 - Normal
Priority:  1 - Later Item Group:  None
Status:  Fixed Assigned to:  None
Originator Name:  Open/Closed:  * Closed
Release:  * dev Operating System:  * Any
Fixed Release:  None Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Thu 08 Aug 2013 07:53:28 PM UTC, comment #2: 

I applied a slightly modified version of your patch.  Thanks.

John W. Eaton <jwe>
Group administrator
Thu 08 Aug 2013 05:24:07 PM UTC, comment #1: 

Update of patch that scrolls only if slider position is exactly at the bottom.  That seems to behave about the same and well enough.

(file #28799)

Dan Sebald <sebald>
Thu 08 Aug 2013 05:01:42 PM UTC, original submission:  

This isn't so much a bug as it is finding the desired behavior. 

If the history always scrolls when a command is issued, the history window has the undesirable property of moving when double-clicking some command far back in the history list when the user probably wants to remain in place and possibly use other nearby commands at that point in history.

If the history never scrolls then at start up its as though history is not being updated.

The attached patch is meant to strike a balance.  If the user ever intentionally scrolls away from the most recent history, the history will not scroll to bottom with a new command.  If the user moves the slider back to the bottom, then it will scroll again with new commands.  That is the general idea.  The algorithm is to scroll if max - value < 5.  Not 5%, but 5.  It seems to be fairly good as an initial start, but there might be similar algorithms.

Can either apply this and see what the response is, or hold off for a bit and see if there isn't something better.  The one dodgy area might be if the user wants to get at commands that are just beyond the upper edge of the history window, i.e., "fairly recent" history and the window keeps scrolling back pushing the desired commands just off the edge of the window.  Since the user is more apt to use fairly history, this might be common.

Could make it an exact bottom, i.e., if max - value < 1, but I'm wondering if users will find that too stringent.  I'll experiment.

Dan Sebald <sebald>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

Attached Files
file #28798:  octave-history_scroll_action-2013aug08.patch added by sebald (1KiB - application/octet-stream)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by jwe (Posted a comment)
  • -email is unavailable- added by sebald (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only group members can vote.

     

    Follow 5 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2013-08-08 jwe Priority5 - Normal 1 - Later
        StatusNone Fixed
        Open/ClosedOpen Closed
    2013-08-08 sebald Attached File- Added octave-history_scroll_action-2013aug08_2.patch, #28799
    2013-08-08 sebald Attached File- Added octave-history_scroll_action-2013aug08.patch, #28798

    Back to the top

    Powered by Savane 3.13-caa5.
    Corresponding source code