-
Notifications
You must be signed in to change notification settings - Fork 7
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
Drop dead code #54
Comments
I only ever used the suppression of the selectability on KTexts and other rendering elements, not on graph element such as labels. As far as I can see this is also never used for labels anywhere in our code, so this could just be removed safely. |
I think the idea was that you usually don't need to create a KText for a label and this way you can configure the selectability of the automatically created KText via the label. However, if it does not work, then we probably don't use it, hence you can delete it. |
Sure. However, I would expect this kind of thing in some convenience API like the KLabelExtensions, not in the runtime. I'll take care about it together with #43. |
KLighD/plugins/de.cau.cs.kieler.klighd.piccolo/src/de/cau/cs/kieler/klighd/piccolo/internal/controller/KLabelRenderingController.java
Lines 96 to 102 in d21bf90
@a-sr @NiklasRentzCAU I would like to remove this code, as
getGraphElement().getProperties().contains(KlighdProperties.NOT_SELECTABLE)
will never be satisfied.getProperties()
returns anEMap<IProperty<?>, Object>
containingIPropertyToObjectMapImpl
s. Hence,KlighdProperties.NOT_SELECTABLE
will never be "contained".Also from a conceptual point of view I don't like these kind of built-in magics.
If I remember right, back then I decided leave the freedom of fine-grained control on the selectability of labels and text fields to the diagram synthesis developers on purpose.
Any objections?
The text was updated successfully, but these errors were encountered: