by chrisjj » Sat Jun 13, 2009 7:50 pm
> a track is still highlighted (yes, technically not selected, but it is differentiated from other tracks by some color), so why should it be disabled?
The command should be disabled because it is inapplicable to the focussed selected object.
> What advantage does disabling it have?
Disabling the command has the advantage of showing the user it is inapplicable to the focussed selected object.
For an app to find some out of focus object that the command could apply it to, and on that basis enable the command, is a recipe for total confusion. The whole point of focus is to direct commands to objects. Without this, a user could never see in advance what object a command would apply to, and could find out only by incurring an unknown risk of experiment. A risk that is substantially greater, note on an app that has no Undo.
> a track is still highlighted (yes, technically not selected, but it is differentiated from other tracks by some color), so why should it be disabled?
The command should be disabled because it is inapplicable to the focussed selected object.
> What advantage does disabling it have?
Disabling the command has the advantage of showing the user it is inapplicable to the focussed selected object.
For an app to find some out of focus object that the command could apply it to, and on that basis enable the command, is a recipe for total confusion. The whole point of focus is to direct commands to objects. Without this, a user could never see in advance what object a command would apply to, and could find out only by incurring an unknown risk of experiment. A risk that is substantially greater, note on an app that has no Undo.