carlito913 / editor-on-fire

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

Bug, BPM, anchoring. #277

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?

1. Load song, grab beat marker, pull to any side, pull of, notes are auto 
arranged to bpm marker.
2. grab bpm marker, pull to any side and cross the noteboard area(2d not 3d. 
lol), pull off -> notes are not auto arranged to bpm marker.

What version of the product are you using? On what operating system?
EOFs from 1.8b33(r903) to 1.8RC7(r1173)

not system depending(i think).

Original issue reported on code.google.com by ul0fka on 29 Jul 2013 at 9:04

GoogleCodeExporter commented 8 years ago
Do you mean this happens when clicking a beat marker and dragging the mouse 
outside of the dark gray area and onto the upper or lower sections (ie. where 
the difficulty tabs or the piano roll are)?  If so, I am aware of this issue, I 
just haven't found a good way to resolve it yet.

Original comment by raynebc on 29 Jul 2013 at 6:05

GoogleCodeExporter commented 8 years ago
Exactly, this issue. It could happen because of Events, repaint or after 
activating some element. so here need add a boo statesmen?

and one more thing about fretboard area seek marker on max zoom... moove it to 
left a little more :)

Original comment by ul0fka on 30 Jul 2013 at 7:21

GoogleCodeExporter commented 8 years ago
If the seek marker looks like it's one pixel off the beat line in some (but 
generally not all) zoom levels, it's a rounding error.  I'm making a small 
change that should fix this.

Original comment by raynebc on 30 Jul 2013 at 7:35

GoogleCodeExporter commented 8 years ago
one more fun on this stuff, on lasted r1177 I'll cam:
drag a note move cursor to left, note going after, when I cross the beat marker 
selection area, it grabs beat marker, now i can change its position and note 
stay still at last position that it had..

fun? yup))

Original comment by ul0fka on 15 Aug 2013 at 5:47

GoogleCodeExporter commented 8 years ago
The editor logic will need to track which region the left mouse button was 
originally activated in (beat marker area, piano roll area), so that if the 
mouse moves into another y coordinate region, the correct manipulations are 
performed while moving the mouse or when releasing the mouse button.

Original comment by raynebc on 15 Aug 2013 at 10:50

GoogleCodeExporter commented 8 years ago
So its almost solved. Let only find a time to code this small stuff :D

Original comment by ul0fka on 16 Aug 2013 at 12:47