4 ms·

Thank you! Yes, a few of the videos have chords marked on tab tracks (e.g., "Chord fingering" on http://www.soundslice.com/yt/Y6ti5f-LHp4/ http://www.soundslice

by adrianh 14y ago

Thank you! Yes, a few of the videos have chords marked on tab tracks (e.g., "Chord fingering" on http://www.soundslice.com/yt/Y6ti5f-LHp4/ http://www.soundslice.com/yt/Y6ti5f-LHp4/) but I'm planning to add a first-class chord track type. To exit looping mode, just press Pause? Or were you just trying to clear a selection? (If the latter, just click anywhere in the timeline canvas.) I have searched high and low for a fix to that two-fingered left scrolling in Chrome, and there doesn't appear to be a way to fix it. :-( If anybody knows, please tell me!

jdunck 14y ago
2-finger scroll: I'm pretty sure this happens when there are no unscrolled bars under the cursor - so how about an old-school JS hack (remember those?): 1) put the annotation inside a container (and make that position:relative); annotation position:absolute, right:0px; 2) autoscroll the container 3) add some JS to infinitely increase the width of the container on a left-ish mouse move. (I think this will still work even if the container is, itself, in a cropping container. I suspect the result will be that 2-finger left swipe will be like quicksand - no apparent movement. Kind of sucks, but less than losing your page. An alternative would be to make history back/forward suck less: keep the display state in local storage and render a page just as it was the last time a person saw it (in terms of time display, modes, and selections). Probably that's a useful thing to do anyway and has Least Surprise in its side.
bdr 14y ago
Calling preventDefault on the mousewheel event stops swipe navigation in Chrome. You may want to restrict this to when the tab pane's scroll position is 0.
- adrianh 14y ago
  I have a preventDefault in there already, and it's still happening. :-/
initself 14y ago
You could display a large picture of the fret layout and the strings for each chord played.

by adrianh 14y ago

jdunck 14y ago

2-finger scroll: I'm pretty sure this happens when there are no unscrolled bars under the cursor - so how about an old-school JS hack (remember those?): 1) put the annotation inside a container (and make that position:relative); annotation position:absolute, right:0px; 2) autoscroll the container 3) add some JS to infinitely increase the width of the container on a left-ish mouse move. (I think this will still work even if the container is, itself, in a cropping container. I suspect the result will be that 2-finger left swipe will be like quicksand - no apparent movement. Kind of sucks, but less than losing your page. An alternative would be to make history back/forward suck less: keep the display state in local storage and render a page just as it was the last time a person saw it (in terms of time display, modes, and selections). Probably that's a useful thing to do anyway and has Least Surprise in its side.

bdr 14y ago

Calling preventDefault on the mousewheel event stops swipe navigation in Chrome. You may want to restrict this to when the tab pane's scroll position is 0.

adrianh 14y ago
I have a preventDefault in there already, and it's still happening. :-/

initself 14y ago

You could display a large picture of the fret layout and the strings for each chord played.