We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
There is already a pressed property, so there can't be a signal with that name.
pressed
Or Do we even need such signal if we have an way to run code on property change (#112) then we would just check the pressed changed action.
The text was updated successfully, but these errors were encountered:
This is going to be one of the main signals of the whole toolkit, so either way I think that it should be as convenient as it can be to use it.
Sorry, something went wrong.
there is a pointer-event callback
No branches or pull requests
There is already a
pressed
property, so there can't be a signal with that name.Or Do we even need such signal if we have an way to run code on property change (#112) then we would just check the pressed changed action.
The text was updated successfully, but these errors were encountered: