Has this been addressed in v10?
IMHO, proper UX should not hide fields/buttons. I think this went back to the original Mac developers guide prior to 1984.
When using the applicability option on a button (grid lines, panel operations, etc.), the false value totally removes the control from the display.
This leaves the user unsure if he/she has ever seen that option before. When viewing a screen, the user can wonder “Isn’t this where that button was? I don’t see it now.” all because a user right or field status has made the control become invisible.
But UX rules should allow a control to be disabled (greyed out, visible but not clickable) to keep users from getting confused.
I did this a long time ago, but you have to change CSS to make the control dimmed and also add a class to disable it. PITA.
Seems like it would be easy to ask if the desire is to (H)ide or (D)isable the control.
