... its purpose was not clear. Comment suggests state update is combined with
drawing, which isn't so and shouldn't be.
So far as I can tell, all it did was make the Mute button flicker, if you
clicked on it and dragged, while the Solo button was up, AND playback or
recording was in progress. But why?
It is a button, not an icon, so it does not need explaining what it is. Also this solves the issue of when the help button is deliberately removed after use.
Fixed by making the smaller buttons a much less strong blue, and using bevelling to make sure there is an edge.
Also reduced bevelling to a less pop-up look, less dark and 1px wide not 2px
Also slightly rounded the larger button corners.
- Darker button backgrounds in toolbars
- More contrast in hover effect, especially for small buttons.
- Mute/Solo have same colour whether track selected or not
- TimeText displays have lighter backgrounds.
Commands flagged with NoAutoSelect will not auto select, even if the user has asked for it. This is used for Cut and 3 different kinds of delete. We later might extend it to fades and repair.
I've implemented three states for what to do if no selection:
0 - Grey out (no longer used)
1 - Auto-select
2 - Give the warning message and try again.
- No longer jumps right when clicked.
- Right edge is now aligned with track name drop down right edge.
- When using just a mute button, the (larger) button is centered.
This is a new problem from Windows 10 Creator's update. The fix fixes it on single monitors, but on dual monitor it may appear first on the main monitor and then jump across.
... Which went wrong in some examples of an effect applied to part of an
envelope that contains only one point; the correct result should have
a level 1 in the selection and unchanged levels left and right of it, no
matter whether the sole point was before, in, or after the selection.
Simplification may still remove that sole point yet still leave the levels
outside the selection correct.
a) 'Ends to Zero Crossings' to 'At Zero Crossings' and move from Region submenu to
root because this is not only a region command and to aid finding and easy access
b) Draw Tool error message recognises again that the tool works in Waveform (dB)
Compute default WaveTrack height analogously to NoteTrack...
Default MIDI track height is enough to display velocity slider...
Make gain slider again visible in default sized WaveTrack
EXPERIMENTAL_MIDI_OUT off -- then no invisible channel buttons...
... using rect.width instead; and making no changes in appearance.
Some routines, like that for the sync lock icon, are pleasingly simplified.
But see comments about some questionable things that may have been based
on the misunderstanding that kTrackInfoWidth was the width between bounding
lines, when in fact, that width was 5 less.
Change some names in TrackArtist to match terminology in TrackPanel
Exclude left, top, bottom margins from rectangles describing TCP
Exclude bottom margin from vruler rectangle reported from FindCell...
Fix a confusion in argument names. No change in behavior
Explanatory comments in TrackPanel drawing; fewer magic numbers
