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

add a generic Interface for releasable Components #2910

Merged
merged 1 commit into from Sep 14, 2019

Conversation

@ramsestom
Copy link

commented Sep 6, 2019

Had to define my own custom buttons and other interactive components so I made a generic Interface for releasable components that any Component that needs to be released by the parent Form can implement.
You are free to add this modification to CN1 if you think it can be usefull to others.

…custom releasable Components (and not just Button) that can be auto released from the parent Form if the user start interacting with them but moves the pointer out of their bounds before the interaction is fully completed
@codenameone codenameone merged commit 597a58e into codenameone:master Sep 14, 2019
1 of 2 checks passed
1 of 2 checks passed
continuous-integration/jenkins/pr-merge This commit is being built
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
@codenameone

This comment has been minimized.

Copy link
Owner

commented Sep 14, 2019

Thanks!
I'll change the IRelease to match our conventions better

codenameone added a commit that referenced this pull request Sep 14, 2019
Clarified the JavaDoc and refactored the interface name to be more consistent with Codename One conventions
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.