-
Notifications
You must be signed in to change notification settings - Fork 188
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
how to deselect a node from controller? #220
Comments
@Hotdog1987 Thanks! |
@rychkog Thank you for a quick look at it. Is there a workaround/hack I can try at this moment? If this is an actual bug then the fix might not be available till it is released. Correct me if I'm wrong. Thing is, we are deep into the project that this needs to be addressed. Thank you. |
@Hotdog1987 I can add the deselect method on the weekend, also I think something like |
@rychkog wow that would be awesome. Thanks alot! |
@Hotdog1987 I've released a new version with an API for allowing, forbidding node selection. Though, this feature is still absent in docs (will add later). You can have a look at the API in here. I hope it is intuitive enough. |
@rychkog Thank you so much for a weekend update. But, I'm little confused about the three new APIs that were introduced. We are seeking for an option to deselect a node from controller not forbidding selection. What is happening now is when I say |
@Hotdog1987 I've released a new version - rc.8 |
@rychkog Thank you alot!!! |
i was reading the documentation and did fair amount of research but could not find a way to programatically deselect a node.
My Scenario:
When user 'left click' a node, a form template needs to show up right below the value. But since it is still part of the node, when user tries to click inside the form, the "node selection" event fires again, triggering the code to select node again.
my template:
my component:
by the way, thank you so much for a flexible yet powerful tree plugin.
The text was updated successfully, but these errors were encountered: