ronso0
ronso0
> or set cues on the wrong track, or set cues at the wrong time > or move knobs and not liking the change. Well, how exactly should Mixxx help...
I understand. I doubt such short fixed time would work, for example if you stretch the beatgrid, then skip through the track to verify it matches the visual beats. IIUC...
I'll close this as fixed, now that #12954 has been merged. > I've also deleted cues off the wrong track multiple times, or set cues on the wrong track, or...
Related #11956
Wooh, that was easier than I expected when I took the first look a while back (actually half the time I spent on debugging stupid mistakes..) This seems to work...
Thanks for taking a look! I did remove commit with (cover) trace logging and temp. stuff. There are small spots I _may_ polish (turn DEBUG_ASSERT into VERIFY_OR_DEBUG_ASSERT) but that doesn't...
Currently rating and color were stored immediately (not saved to tracks of course). I'm about to change that so all properties are handled consistently, i.e. apply all changes to track...
Please let me know when someone starts reviewing.
Thanks for testing! > there seems to remain some warning noise when editing fields. What are you referring to?
Re: multi-valued fields I thought, as first implementation, the italic/regular font would be sufficient to signal the IS and NEW (edit) state. I don't know which separator to choose that...