m0j0hn / editor-on-fire

Automatically exported from code.google.com/p/editor-on-fire
Other
0 stars 0 forks source link

New notes don't always automatically select #231

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
If I place a note in one difficulty, and then place a note at the same position 
in another difficulty in a pro guitar track, the latest note doesn't 
automatically select.

Original issue reported on code.google.com by raynebc on 28 Jan 2011 at 5:33

GoogleCodeExporter commented 9 years ago
It's probably selecting the note that was originally placed since it is at the 
same position. If this is what I think it is I know exactly where in the code 
to look and it should be an easy fix.

Original comment by xander4j...@yahoo.com on 7 Feb 2011 at 3:56

GoogleCodeExporter commented 9 years ago
I tried reproducing this issue using Piano Roll input but the new note is 
always selected. The selection code is the same for all types of tracks so if 
there is an issue it should be present in non-pro tracks as well.

Original comment by xander4j...@yahoo.com on 9 Feb 2011 at 11:51

GoogleCodeExporter commented 9 years ago
I was able to reproduce this in PART GUITAR with Classic, Piano Roll, Hold and 
Rex Mundi input methods.

Original comment by raynebc on 11 Feb 2011 at 3:21

GoogleCodeExporter commented 9 years ago
I think it's very likely that this is caused by the same thing that caused 
issue 236:  The selection array is invalidated by the sorting that occurs when 
creating a new note.  In this is the case, this would only be experienced with 
tracks that had notes in multiple different difficulties.

Original comment by raynebc on 4 Mar 2011 at 10:36

GoogleCodeExporter commented 9 years ago
Probably due to the changes since 1.8b2, I am now no longer able to reproduce 
this, so I'll consider it fixed.

Original comment by raynebc on 4 Mar 2011 at 10:41