Community
Participate
Working Groups
Potentially add input validation with decorator.
Created attachment 184916 [details] patch v1 First try on an attribute editor along with a suggested integration in the framework Let me know what you think of that Steffen
Created attachment 184917 [details] mylyn/context/zip
Thanks Thomas. This looks promising. I have opened bug 332328 to track the API portion of the change. Once that is resolved I am happy to apply a patch based on the new API.
Created attachment 184978 [details] patch v2 (depends on bug 332328) (depends on bug 332328) includes fix for bug 329575 as well
Created attachment 184979 [details] mylyn/context/zip
Committed as part of bug 329575. *** This bug has been marked as a duplicate of bug 329575 ***
On further review this needs a little bit more work. Values should be retrieved and modified through TaskAttributeMapper. I have added methods to support attributes of type double. Can you make the corresponding changes to the patch? You can use BooleanAttributeEditor.get/setValue() as a guideline.
On second thought, let's go with this patch. Otherwise, invalid value would be discarded on save. We might need to reconsider the current design in the future but generally I believe it's better to allow entering of invalid values and handle this on submit (bug 242430).