Yes, I want the last selected mixer strip(s) to be highlighted in both the
mixer and arranger. Being able to CTRL-click to highlight multiple would
definitely be a plus too. Maybe I should add that to the issue ticket?
The modifying multiple controls at once idea sounds good to me. I presume
it would work by increasing or decreasing the selected controllers by the
same amount, rather than making sure the selected controls get reset to the
same value and then adjusted in unison although I seriously doubt you
intended the latter.
On Tue, Jan 19, 2016 at 3:05 AM, Tim E. Real <[email protected]> wrote:
> On January 18, 2016 10:10:08 PM Dan MacDonald wrote:
> > Yep - looks good to me! Thanks Robert! The Issue has been closed. :)
> >
> > None of you have commented on my track highlighting feature request yet.
> I
> > presume everyone agrees this is useful but is it tricky to add without
> too
> > much mixer churn?
>
> You mean the suggestion of highlighting the strip that's currently
> selected?
>
> Yes, thinking about it.
> It ties in with the editable strip label idea too.
>
>
> The thing is, something I am working on ATM may prove useful here:
>
> I am going to allow editing of multiple-selected tracks' common properties.
>
> That is, select several tracks in the arranger, and edit one of their
> properties and /all/ of the selected tracks are affected.
>
> (Similar to how object-oriented apps like say QTDesigner or
> Borland C++Builder work.)
>
> Users and devs may notice a first step done:
>
> I have now added a 'currentSelected()' method to class trackList.
>
> It's all automatic. It does what it says.
> You select stuff and it ensures that currentSelected() always returns
> the most recent selected track (or nil).
>
> So, my first usage of this feature, is to ensure that in the
> arranger track list, the panel shown in trackinfo is now always
> the /latest/ track clicked. You may have noticed this was /not/
> the case before, and was wacky in that it depended on whether
> you clicked midi or audio tracks.
>
> This is an important first step for common-selected-property editing.
>
>
> So... anyway, I am thinking as it related to the mixer:
> We could have /multiple/ selected strips, and whatever you
> edit on one strip applies to /all/ selected strips.
> Provided of course that the particular edited property is
> a common property of each of the other selected strips.
> That's how these common-selected-property things are done.
>
> Whaddya think?
>
> Tim.
>
> >
> > On Mon, Jan 18, 2016 at 2:18 PM, Robert Jonsson <[email protected]>
> wrote:
> > >>>> Couple of quick thoughts for the mixer if possible:
> > >>>> 1) In Arranger mode the synchronization should be bidirectional,
> > >>>>
> > >>>> both mixer and arranger should agree.
> > >>
> > >> Yeah, Dan brought that up also, I'll try to fix that.
> > >
> > > Turned out to be incredibly easy so I wonder if I got it right..
> pushed to
> > > master.
> > >
> > > Regards,
> > > Robert
>
>
>
> ------------------------------------------------------------------------------
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
> _______________________________________________
> Lmuse-developer mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/lmuse-developer
>
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
Lmuse-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lmuse-developer
