Re: Mouse & Keyboard properties...



> > I was just thinking... Why not merge the 'Keyboard Properties' and
> > 'Mouse Properties' programs and make one called 'Input Properties'?
> > With click-tabs named 'Mouse' and 'Keyboard'.
> 
> This would be more intuative, however...
> It would need to be easily extended - Watcom tablets come immediately to
> mind.
> 
> IMHO, having a well balanced tree for a menu is more desirable - keeps
> some things from getting too deep or too shallow.

In that case, why not dith the click-tabs? It's totally meaningless to
have click-tabs when there's only a single click-tab in a window.
The only thing it does is take up display-space. People that run X in
1600x1200 might think it's neat, but for people running 800x600 it
takes upp way to much space. 

Anyway, you could make it extendable. First, you would strip the 
properties-apps from the click-tabs and the OK/Apply/Exit buttons.
Then, you would make a different properties-app that just has the
click-tabs and OK/Apply/Exit buttons. It could then "swallow"
the other properties-apps in the same way the panel does.
Whoila! You've got an extensible properties-dialog! 
The main app would ofcourse need to signal the swallowed apps that
the user "wants to save now" and such. 

Any thoughts?
 
-- 
Adam Chodorowski (archmage@earthdome.com)



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]