[Rosegarden-bugs] [ rosegarden-Bugs-1274686 ] Yet some repeating segment bugs

[SourceForge.net <no...@so...>]

Bugs item #1274686, was opened at 2005-08-27 17:21
Message generated for change (Comment added) made by yguillemot
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=104932&aid=1274686&group_id=4932

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: gui
Group: None
Status: Open
Resolution: Fixed
Priority: 7
Submitted By: Yves Guillemot (yguillemot)
Assigned to: Guillaume Laurent (glaurent)
Summary: Yet some repeating segment bugs 

Initial Comment:
 
1 - Create a one bar segment ((A) : track 1, bar 1) 
2 - Create another one bar segment ((B) : track 1, bar 7) 
3 - Select (A) segment and make it repeating 
    ((A) segment is correctly repeating 5 times, until the 
begining of (B) segment) 
4 - Move (A) segment to track 3, bar 3 
     ==> Bug 1 : (A) segment is still repeating only 5 times 
(it should be repeating to the end of the composition) 
5 - Move (A) segment to track 3, bar 1 
     ==> (A) segment is now correctly repeating to the end 
of the composition ! 
6 - Move (A) segment to track 1, bar 1 
     ==> Bug 2 : (A) segment is always repeating to the end 
of the composition (it should be repeating only 5 times, 
until the begining of (B) segment) 
7 - Try to select (B) segment 
     ==> Bug 3 : (A) segment is always selected in place of 
(B) segment 
 
 

----------------------------------------------------------------------

>Comment By: Yves Guillemot (yguillemot)
Date: 2005-08-29 20:17

Message:
Logged In: YES 
user_id=769617

It's far better, but still not perfect : 
  A correct behaviour is now obtained when moving a repeating 
segment. 
 
But : 
 - Moving a non repeating segment after a repeating one (on the 
same track) doesn't stop the repetition. 
 - If the segment moved after a repeating one was itself 
repeating, it is displayed as a long non repeating segment. 
 

----------------------------------------------------------------------

Comment By: Guillaume Laurent (glaurent)
Date: 2005-08-28 21:07

Message:
Logged In: YES 
user_id=4816

*sigh*, sorry, I actually broke the fix just before committing it, 
thinking I was getting rid of unneeded  variables. Very very stupid. 
re-update compositionview.cpp, it should work now. 

----------------------------------------------------------------------

Comment By: Yves Guillemot (yguillemot)
Date: 2005-08-28 20:51

Message:
Logged In: YES 
user_id=769617

 
The fix is not working for me :      
 
When, in step 4, (A) is moved, the result depends of destination 
bar : 
  - bar 1 : OK (repeating to end of composition) 
  - bar N (N > 1) : 1 segment repeated only 5 times. 
      New issue : the first (original) segment has the same gray 
color as the others 
  - bar N (N > 2) : N-1 "green segments" are preceeding the 6 gray 
segments 
 
(A) segment can't be selected by clicking on it's green part (the 
gray part has to be used).  
      
Maybe a non related bug :  
Doubleclicking on a (A) segment gray part doesn't open the 
default editor, but duplicates the segment on the same track. 
Bar of new created segment depends of initial segment bar and 
clicking place : If gray part of segment begins in bar N, 
doubleclicking on bar M creates a new segment in bar M-N+1.    
 

----------------------------------------------------------------------

Comment By: Guillaume Laurent (glaurent)
Date: 2005-08-27 18:39

Message:
Logged In: YES 
user_id=4816

It's was in my code, fixed in cvs. 

----------------------------------------------------------------------

Comment By: D. Michael McIntyre (dmmcintyr)
Date: 2005-08-27 18:09

Message:
Logged In: YES 
user_id=663564

I confirmed all of these, but they aren't really a problem with G's new 
code, I don't think.  I don't have a 1.0 around to test with, but I 
remember that 1.0 had similar, if not identical problems. 
 
The workaround in all cases where this misbehaves is to cycle the 
repeat state for the offending segments.  Everything should get 
re-drawn correctly after doing that. 
 
These are real problems, but I don't think they're release critical, 
there's a reliable workaround, and so I'm giving this a priority of 7.  
"serious - less significant usability problems, broken features" 
 
Thanks for reporting your findings. 
 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=104932&aid=1274686&group_id=4932