Re: [Protux-devel] regarding BusMonitor

[Luciano Giordana]

Honestly, I think I changed my mind. I dont think the splitter should be 
removed. This is why.

Jmb actions are supposed to be directed to audio editing, not interface 
adjustments. The reason is that normally a user tends to keep the interface 
always in
a same way and never changes it. We would be spending a central key (B) to a 
very unsed action.
B would be central key bus selection/bus level adjustment, and other bus stuff, 
but not the bus widget which can be "clicklly" adjusted.

We dont want to kill ALL clicks, we want to kill as much as we can. But how 
worthy is to eliminate the bus monitor clicks right now, and keep the FS clicks 
?

lets reserve the letter (A-Z) to very used actions. Those interface adjustments 
could also be jmb oriented, but in the future, in a special mode, like , you 
<IA> (Interface adjustments) 
then all actions will adjust the interface, then you get back to work with 
<ESC> , and so on...

RFC, and sorry if you have already worked on eliminating splitter :-}


On Monday 20 October 2003 18:07, Remon Sijrier wrote:
> On Monday 20 October 2003 17:03, Luciano Giordana wrote:
> > Im sorry, let me make myself more clear. The problem is not only the 
> > width (50%) but the fact that I cant "close" cardinfo area as I could
> > when it was in the splitter.
>
> Ah. Do you have a suggestion for a jmb action?
> Then it's better I think to allready remove the QSplitters from BM and
> handle the show/hide only_vus_in/out actions by jmb
>
> The the rest can be later done when BM has its own jmb engine, and move BM
> jmb stuff from Song into it. RFC
>
> Remon
>
>
>
> _______________________________________________
> Protux-devel mailing list
> address@hidden
> http://mail.nongnu.org/mailman/listinfo/protux-devel

-- 
Best Regards
--
Luciano Giordana
Project Mustux - Musician Tools for GNU/Linux
http://www.freesoftware.fsf.org/mustux