Community
Participate
Working Groups
In some cases the CompletionCombo does not fire selection events -- where the original CCombo would fire them. - text match in the text field - text match pasted into the text field - text match from the list Also we should consider these cases: - text edited in the text field, no match - text edited in the text field, new match - text cleared in the text field - text cleared via cut operation in the text field - text set via API (setter)
Created attachment 189565 [details] Snippet
Created attachment 189566 [details] Patch v1
Patch was doing to much. Committed different version. Essentially: - user interaction triggers selection events. This means: klicking on the list, using arrows on the list or text, using mouse wheel on the list or text, typing in the text field (if a new item is selected as a result, or the selection is cleared because no match), deleting the text (=empy = no match) - API interaction does not cause selection events. I.e. select(...), deselect(...), deselectAll(). This is consistent with what SWT does and prevents stack-overflows when listeners invoke such API.
Created attachment 190007 [details] Updated patch
Resolved
