Community
Participate
Working Groups
The data FormToolkit.KEY_DRAW_BORDER is only set to false if the attribute is read-only and is never set to true if it is editable. On Linux, this results in fields that have no border so it is difficult to tell if the field is editable or not.
Created attachment 117025 [details] patch Here is a patch that adds the draw borders data and paints the borders for the composite that the text was created on. Steffen, does painting the borders everytime an attribute editor is created affect the performance?
Created attachment 117026 [details] mylyn/context/zip
Good catch. I have applied the change that sets border flag. Painting borders should be invoked by the class using the attribute editor. This is generally done in the editor parts, e.g. toolkit.paintBordersFor(attributesComposite) in TaskEditorAttributePart.expandSection() . Let me know if that doesn't work for you.
(In reply to comment #3) > Good catch. I have applied the change that sets border flag. Great! > Painting borders should be invoked by the class using the attribute editor. This > is generally done in the editor parts, e.g. > toolkit.paintBordersFor(attributesComposite) in > TaskEditorAttributePart.expandSection() . Let me know if that doesn't work for > you. Yup, this was my fault. The paint borders isnt needed in this patch.