bugDenemo - Bugs: bug #32342, d-GoToPosition - bugs and problems...

 
 

bug #32342: d-GoToPosition - bugs and problems because it guesses the next best position

Submitter:  -Deleted Account- <steele>
Submitted:  Thu 03 Feb 2011 07:47:27 PM UTC
   
 
Category:  None Severity:  3 - Normal
Item Group:  None Status:  Fixed
Privacy:  Public Assigned to:  rshann
Originator Name:  Open/Closed:  Closed
* Mandatory Fields

Add a New Comment Rich Markup
   

Fri 04 Feb 2011 10:43:21 AM UTC, comment #2: 

An empty measure is already correct, it has one position "1", Appending. There are no positions "0" in this context at all.

The other question is, what if you GoToPosition 3 and the target is an empty measure. The answer remains the same.

Return #f, stay where you are. No guessing what might be a good place to go to.

Again: if we want a smart command we can do it in Scheme. But we need one command that is strict. If the position is not there you simply cannot go to it.

-Deleted Account- <steele>
Fri 04 Feb 2011 09:45:31 AM UTC, comment #1: 

This command has not gone into a release yet so we can change its semantics.
Before doing so, can we clear up desired behavior with position number when target measure is empty? I think at present you can ask for either 0 or 1

Is this good?

Richard Shann <rshann>
Group administrator
Thu 03 Feb 2011 07:47:27 PM UTC, original submission:  

d-GoToPosition should not try to be smart and guessing but rather be exact:

If you do
(d-GoToPosition #f (1+ (d-GetStaff)) #f #f)
which is the same as
(d-GoToPosition (d-GetMovement) (1+ (d-GetStaff) (d-GetMeasure) (d-GetHorizontalPosition))

it goes down one staff but remains on the horizontal position which would be a nice default behavior for our current "Staff Down" keys.
However:

If there is no such measure (unequal staff length) the next left measure is taken and #t is returned.
I think there should be no movement in this case. If the exact position cannot be reached d-GoToPosition should refuse to work.

HoritontalPosition not existent is related. The cursor jumps to the first position in the target-measure, but this times returns #f.

If we want smart, guessing command we should script them. I consider the current situation as bugs.

Related, but solved after changing the above:
If you GoTo a horizontal position 3 (or any other) to where no such position exists the cursor will jump to the first object in that measure and the statusbar tells you you are on position 3.
MoveCursorLeft (the left arrow key) is then deactivated, but not MoveCursorRight. Once you go right and left again a few times you can move freely.

-Deleted Account- <steele>

 

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

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by rshann (Posted a comment)
  • -email is unavailable- added by steele (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 logged-in users can vote.

     

    Follow 4 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2011-03-01 steele StatusNeed Info Fixed
        Open/ClosedOpen Closed
    2011-02-04 rshann StatusNone Need Info
        Assigned toNone rshann

    Back to the top

    Powered by Savane 3.13-758e.
    Corresponding source code