Hi there, > From: Hendrik Jan Veenstra <h@...> > > Thoughts from the mind of Jonathan Christensen, 25-03-2002: > >> Hmmm . . I think your description of event-mute is the most intuitive, >> and >> least likely to wreak havoc. A mute button . .it stays muted when >> collapsed >> . .and is indicated as such by italisized type in the list > > Uh.. yes, sounds like a simple way out indeed :-). So Italic could > either mean "entire track muted' or "section of the track muted". Or maybe it is easier to make the mute button look like an itemized check list. i.e., when an item that has sub-items is ticked, for example, it means that all enclosed items are also ticked. If one of them in the group is not ticked then the group item has a dash or hyphen to show that all items are not ticked. Now, I would think that you'd want some way of muting all items in a group with one click - i.e., muting the main item mutes all those in the group. Otherwise, muting individual items within the group, while the main item is unmuted, would result in the main item displaying a dash (or hyphen) so that you know that one or more of the enclosed items is muted - but not all items. If all items were muted then the main item would display this as a full mute. So, normal operations on this would be: If one or more, but not all, items in the group are muted, then clicking once on the main item - to mute all - and then again will unmute all and therefore allow an easy reset. Or maybe this is better as an Opt/mac+click or Ctl/win+click to do a reset... But this seems to me to be the logical use of lists with checked items. So when the sub-items are hidden, you still can mute/unmute them all by controlling the main item's mute. >> The problem with the other method . . "hiding an automation track >> unmutes >> it" . . . is that there is nothing else currently in the program that >> behaves similarly. That is, we would be placing the burden on Logic to >> remember the mute status based purely on visibility. Then there is >> screen >> sets to deal with, and even whether track automation is even currently >> active. > > Argh... you're SO right... I hadn't considered screensets and such > *at all*. Yes, of course, my proposal would be totally unworkable... Screen sets should effect the status of a track being armed or not. Only whether or not you see that track on the screen-set. > cheers, > HJ > -- > Hendrik Jan Veenstra <h@...> > Omega Art: http://www.ision.nl/users/h/index.html with regards, -- Lachlan Deck ldeck@...