-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
I would like to be able to disable widget.List #1499
Comments
We don't have this feature at present. What would a disabled List look / behave like? |
Like disabled |
I'm not sure what we can turn gray - in this instance all the contents are controlled by the app developer. |
Disabling user interaction for selection and hover would make sense, but I would be hesitant of disabling user interaction for scrolling. How would this apply to future keyboard navigation/interactions? |
I guess the disabled list should not be focusable, but I'm not sure. |
@andydotxyz BTW Is there a master GitHub issue for keyboard navigation support? It looks like soon I will desperately need this features in my software, so I would like to see at least some spec as you maintainer guys see it. May consider to participate in this development. |
Sadly we have not pulled one together, that is a good idea. |
I have now added the keyboard tag, that will gather keyboard nagivation issues :) |
In planning Bowmore we came by this ticket but could not tell what was really needed. |
Worth noting that you can easily achieve this with an extended List, just adding the Disableable interface methods. By default this does nothing other than preventing it from being focused by the focus manager. This, combined with making your list items handle Tapped, can completely disable selection on the list. To make it grayed out when disabled, have your extended list render with a rectangle on top of the base list, which is semi-transparent gray for disabling, or hidden when not disabled. |
I'm tempted to close this now there is a known way to do it in user code. As posted earlier I don't really think there is a case for making standard widgets disabled that are not input widgets (or buttons) |
I agree. Closing this as it's possible to achieve the desired behavior in user code. |
Can this be done?
The text was updated successfully, but these errors were encountered: