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

Texts are not selectable by default anymore and therefore causes unexpected behavior in combination with selectability suppression #123

Open
NiklasRentzCAU opened this issue Jun 2, 2022 · 0 comments
Labels
bug Something isn't working

Comments

@NiklasRentzCAU
Copy link
Member

In earlier versions of KLighD different elements were selectable: nodes, lables, ports, edges and texts. Texts are not selectable on their own anymore and instead select the e.g. node that is the parent of the text rendering. I do not really mind this behavior, but is a bug if individual text selection should still be a feature.
This leads into another problem with the suppressSelectablility method or resp. the NOT_SELECTABLE property for texts.
Its documentation states, that "if done the KText can't be selected anymore", indicating that texts should be selectable.

Currently if text within node renderings is clicked, the node is selected instead. If the selectability furthermore is suppressed on that text, the node is still the selected element, however now the text will also get its selection style applied as it is selected together as part of the node, causing a seemingly inverse behavior of this property - in that suppressing the selectability enables the selection style to appear.

@NiklasRentzCAU NiklasRentzCAU added the bug Something isn't working label Jun 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant