arrow key implementation
Posted: Thu Sep 07, 2006 2:32 am
Stop me if you have heared this one before.....
I realise that there is a subtle balance between implementing new suggestions and making the software SO tailorable that it becomes unusable, but here is my suggestion for what its worth.
How about implementing the arrow-key cluster for VOLUME up/down and PAN left/right.
I find that jump-next and jump-back are seldom used and are covered by click buttons anyway. Also can the hotkeys panel be made unselectable for those of us who NEVER use it? (ALL our sound cues are programmed and sequenced.)
That aside, it's a truly great bit of software, we have come over to it from Q-Manager which has (sadly) suffered from lack of developement dispite it's high price tag.
I realise that there is a subtle balance between implementing new suggestions and making the software SO tailorable that it becomes unusable, but here is my suggestion for what its worth.
How about implementing the arrow-key cluster for VOLUME up/down and PAN left/right.
I find that jump-next and jump-back are seldom used and are covered by click buttons anyway. Also can the hotkeys panel be made unselectable for those of us who NEVER use it? (ALL our sound cues are programmed and sequenced.)
That aside, it's a truly great bit of software, we have come over to it from Q-Manager which has (sadly) suffered from lack of developement dispite it's high price tag.