Hi Michel, first, it should not be a need to create your own component for this kind of usecase. Changing to have this feature sounds more like adding a new attribute to the component.
Since tying inputSuggestAjax to dojo, the component is still under construction; i have invested my time to get the new tableSuggest to work, so sorry but not so much time to spend on it. I know there are still some open issues for it (like styling and of course your suggested feature; i have recognized the same problem a few days ago) and hopefully i get them to work the next two weeks. Till the new inputSuggestAjax will work as it is also satisfying for me, i would suggest relying on the old component (if you are not depending on the nightly builds) or the new tableSuggest which should also work fine. regards, Gerald On 3/7/06, Michel Goldstein <[EMAIL PROTECTED]> wrote: > Hi, > > I was using the "old" InputSuggestAjax for autocompletion that accepted > receiving the beginning of the middle word of a phrase. For example: > > Entering "m" would give me: > > "know my components" > "MyFaces" > "oh my!" > > However, in the new version of the component, it automatically picks up the > first word and assumes that you typed the first letter of this word. For my > example above it would add to the text box "k|now my components" (the "|" > symbol is where cursor would be) and then suddenly it would think that I > actually entered "k" instead of "m" and recalculate all my suggestions for > "k". > > Is this a valid use case for the new component and it doesn't work right now > because it's still in development phase? Or should I plan to stick to the > old component or create one of my own to deal with this use case? > > Thank you, > Michel > -- Gerald Muellan Schelleingasse 2/11 1040 Vienna, Austria 0043 699 11772506 [EMAIL PROTECTED]
