feat: Add support for disabling specific virtual keyboard keys with customizable appearance. #4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
feat: Key Interaction Control (Enabled Keys Whitelist)
Summary
This PR implements a robust key interaction control system based on a whitelist approach. It introduces
enabledKeystoVirtualKeyboardController, allowing developers to restrict keyboard input to a specific set of keys.🚀 Features & Changes
API Refactor (Based on Feedback)
disabledKeysparameter was removed from the widget. Instead,enabledKeys(Set<VirtualKeyboardKey>?) is now a property ofVirtualKeyboardController.null: All keys are enabled (default).Set<...>: Only keys in the set are interactive. Use this to restrict input (e.g. for a game or validation).🛠 Implementation Details
Set<VirtualKeyboardKey>to ensure type safety and eliminate string parsing overhead during render.disabledBackgroundColor,disabledForegroundColor) to visually distinguish disabled keys.Verification
dart analyze.Usage Example