I wonder: is it a good idea to change the "affects version" label for these issues? I mean, they do affect 2.1, and since they haven't been fixed it's reasonable to assume that they affect 2.2 also. Is there an advantage to changing this?
--Thilo Marshall Schor (JIRA) wrote: > [ > https://issues.apache.org/jira/browse/UIMA-458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Marshall Schor updated UIMA-458: > -------------------------------- > > Affects Version/s: (was: 2.1) > 2.2 > > Won't be fixed for 2.2 > >> For creating new UIMA descriptors in Eclipse, make accelerator keys work >> better >> ------------------------------------------------------------------------------- >> >> Key: UIMA-458 >> URL: https://issues.apache.org/jira/browse/UIMA-458 >> Project: UIMA >> Issue Type: Improvement >> Components: Eclipse plugins >> Affects Versions: 2.2 >> Reporter: Marshall Schor >> Priority: Trivial >> >> If you use keyboard shortcuts to create a new UIMA component, things don't >> quite work because many of the UIMA components get "filtered" by the >> keyboard keys. This may be fixable with proper accelerator key >> specifications. >> Failing case for example: >> 1) select a Java project >> 2) press (assuming normal key bindings) ALT - f - n - o - u which is short >> for: >> menu - File - New - Other - filter by "u". This shows the UIMA folder under >> "other", and also expands it, but filters it to only show strings containing >> words which start with a "u". So no component show up. >
