O yeah, but I need to know what has triggered it. Escape, click outside of dropdown, selection?
Any reason why the
triggerEvent property of the close event doesn't work?
Dont know any except a bug. When I check it in my close event handler, it has a value of a null.
Yeah, in my experience creating the Flextras AutoCompleteComboBox I noticed that in many cases, that triggerEvent is never passed to the close method.
I never dealved into why that was, but assumed it was by design.
You may have to extend the ComboBox and do some tweaking to figure this out yourself. I'd start by looking at the focus handlers and/or collection change handlers.
Or if you expand on what you're trying to accomplish maybe we can offer alternate approaches.
Yes, I am working with autoComplete. When I type something in that matches (or matches partially) available choices the control presents first available match in the text area. The presented text comes up partially highlighted. If I hit escape at this point the highlighted portion is deleted while the control keeps its data unchanged. I want to either prevent hitting escape altogether or remove the selected text completely to force the user to select something again.
To control the escape key, you're going to have to override the Key Press handlers.
But, If I can put on my self-promotion hat for a moment:
I bet you'll save a lot of time if you just use the Flextras AutoCompleteComboBox instead of trying to roll your own: http://www.flextras.com/?event=ProductHome&ProductID=10
We spent a lot of time into making ours work just like the Firefox Awesome bar.
Here is one of our samples, which allows you to explore the API and see how things changed based on property settings:
The escape key, while typing in the AutoComplete TextInput is ignored.
A developer edition is available for no cost at www.flextras.com.
Yeah, I am looking at your samples and I dont an exact behavior as the Adobe's autoComplete.
when I type, your control does not place any matching text into typing area. I have to choose it from the dropdown portion.
Am I testing it wrongly?
I'm not sure if I completely understand the issue you are seeing.
I took a look at the Adobe AutoComplete ( http://www.adobe.com/cfusion/exchange/index.cfm?event=extensionDetail&extid=1047291 ) sample ( http://examples.adobe.com/flex2/exchange/AutoComplete/CustomizeAutoComplete/CustomizeAutoC omplete.html ).
Are you looking for the "look ahead" functionality? If so, that was not implemented in the Flextras AutoCompleteComboBox. In all the AutoComplete's we looked at, I've never seen one that highlights items like that. After a minute of experimenting I can see why. It just feels buggy.
Can you provide a UI precedent for this form of 'look ahead' in an AutoComplete?
<Are you looking for the "look ahead" functionality?
<Can you provide a UI precedent for this form of 'look ahead' in an AutoComplete?
Not sure what you are asking me.
1 person found this helpful
Sorry, I was unclear.
I was asking for an AutoComplete implementation in the real world that has "look ahead" Functionality as implemented in the Adobe AutoComplete?
The Firefox AwesomeBar does not provide look ahead.
The YouTube search box does not provide look ahead
Firefox Search Bar does not provide look ahead
Gmail address fields do not provide look ahead
Google.com Search Box does not provide look ahead
If we were to implemnt this for the Flextras AutoComplete, what would we model it after? Who else is using this sort of feature? How will users react to it? Will it be familiar / obvious or confusing?