Community
Participate
Working Groups
It would be really nice if it will be possible to set selection in FieldAssist's dropdown list. So could you please change visibility of ContentProposalAdapter.selectProposal(int index) to public.
API is frozen for 3.3, but we can consider this for next round
will consider for 3.4
investigate/fix for M3.
Doing this is a bit more involved than merely changing method visibility. The ContentProposalPopup implementation is private, so any API provided would have to be at the ContentProposalAdapter level. Further, using indexes as the specification for selection in the API is a bit vague since there are issues of filtering to take into account. An index would be rather short lived and we would have to define the life cycle of the API...does it mean set the selection the next time the popup is opened? select only if opened? etc. etc. Would you be calling this when receiving a listener event (popup opened?) Is this something contextual to the state of the control and popup or is it something where the proposal provider itself could provide information about the default selection. Bottom line is that defining the behavior/life cycle of the API is rather detailed and I would need to understand the end user scenario you are trying to accomplish so that I can determine if this is something of general purpose.
Removing milestone and marking WONTFIX. I don't see any user scenarios where forcing a selection really makes sense. It's really outside of the model of the field assist popup. If what you are after is pattern matching and ensuring that the closest match of a particular pattern is the one selected, then this should be done at the level of ContentProposalAdapter. For example, platform text achieves this with the RegExpContentProposalAdapter, by ensuring that the order of the proposals always puts the best match first. Please reopen if I am misunderstanding the request.
I'm implementing the tool for working with exchanges and use content assist for price fields. And want to say that it's very natural for traders to see in content assist something like: <current_price> - 3 <current_price> - 2 <current_price> - 1 <current_price> <-- default selection <current_price> + 1 <current_price> + 2 <current_price> + 3 A lot of traders use to work in this way. The only one alternative I could see at the moment is to use the following: <current_price> <-- default selection <current_price> + 1 <current_price> + 2 <current_price> + 3 <current_price> - 3 <current_price> - 2 <current_price> - 1 in this case up/down arrows will work in the same way but don't you agree that first list looks much more natural even for ordinary people.
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
