Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Setting locked for access level" is not shown when expected #1766

Closed
blammit opened this issue Nov 27, 2024 · 2 comments
Closed

"Setting locked for access level" is not shown when expected #1766

blammit opened this issue Nov 27, 2024 · 2 comments
Assignees
Milestone

Comments

@blammit
Copy link
Contributor

blammit commented Nov 27, 2024

When the user tries to edit a control that is locked for the current access level, the UI should show a "Setting locked for access level" notification.

This is currently only implemented for radio-button options.

@blammit
Copy link
Contributor Author

blammit commented Jan 15, 2025

This depends on the enabled changes in #1876.

MikeTrahearn-Qinetic added a commit that referenced this issue Feb 7, 2025
Document its rules of operation for all derived types.
Should always be enabled - use interactive property to
change the inner child items under the documented rules.
Interactive should be false unless required.
Should be clickable - derived types no longer need to
implement their own ListPressAreas.
Should consider Global.systemSettings.accessMode for future use in #560
Show a generic toast for settings locked for access level #1766

Part of #1818
Fixes #1766
MikeTrahearn-Qinetic added a commit that referenced this issue Feb 12, 2025
Document its rules of operation for all derived types.
Should always be enabled - use interactive property to
change the inner child items under the documented rules.
Interactive should be false unless required.
Should be clickable - derived types no longer need to
implement their own ListPressAreas.
Should consider Global.systemSettings.accessMode for future use in #560
Show a generic toast for settings locked for access level #1766

Part of #1818
Fixes #1766
MikeTrahearn-Qinetic added a commit that referenced this issue Feb 12, 2025
- Document its rules of operation for all derived types.
- Should always be enabled - use interactive property to
  change the inner child items under the documented rules.
- Interactive should be false unless required.
- Should be clickable - derived types no longer need to
  implement their own ListPressAreas.
- Show a generic toast for settings locked for access level #1766

Part of #1818
Fixes #1766
MikeTrahearn-Qinetic added a commit that referenced this issue Feb 13, 2025
- Document its rules of operation for all derived types.
- Should always be enabled - use interactive property to
  change the inner child items under the documented rules.
- Interactive should be false unless required.
- Should be clickable - derived types no longer need to
  implement their own ListPressAreas.
- Show a generic toast for settings locked for access level #1766

Part of #1818
Fixes #1766
MikeTrahearn-Qinetic added a commit that referenced this issue Feb 17, 2025
- Document its rules of operation for all derived types.
- Should always be enabled - use interactive property to
  change the inner child items under the documented rules.
- Interactive should be false unless required.
- Should be clickable - derived types no longer need to
  implement their own ListPressAreas.
- Show a generic toast for settings locked for access level #1766

Part of #1818
Fixes #1766
MikeTrahearn-Qinetic added a commit that referenced this issue Feb 17, 2025
- Document its rules of operation for all derived types.
- Should always be enabled - use interactive property to
  change the inner child items under the documented rules.
- Interactive should be false unless required.
- Should be clickable - derived types no longer need to
  implement their own ListPressAreas.
- Show a generic toast for settings locked for access level #1766

Part of #1818
Fixes #1766
@MikeTrahearn-Qinetic
Copy link
Contributor

Closed automatically due to the work done to solve #1876

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants