14 replies to this topic

[Marc]

Hi,

I think it will be cool to add a "Autocomplete" property on TNXComboBox to complete input automatically with strings found in combo list.

Like standard TComboBox

[emailaya]

u already have the TnxAutoComplete component
that u can attach to any component u want

[Boki (Berg)]

Hello,

Yes, this component is located in Packages\NxAddonsRun.dpk package (great thanks to Wim).

If you wish, I may add property AutoComplete to point to NxAutoComplete component?

regards

[emailaya]

add an autocomplete to nxcombobox?

but currently autocomplete has a link to a component
which is more generic, i think it should stay that way

[Marc]

u already have the TnxAutoComplete component
that u can attach to any component u want

In DBGRid, it's not automatic, we must add lines code in events to work with it

Hello,

Yes, this component is located in Packages\NxAddonsRun.dpk package (great thanks to Wim).

If you wish, I may add property AutoComplete to point to NxAutoComplete component?

regards

It would be well !

[Boki (Berg)]

Hello,

In that case, NxAutoComplete must be added to NxCommonRun package.

regards

[wvd_vegt]

Hi All,

In that case, NxAutoComplete must be added to NxCommonRun package.

Some remarks on Autocompletion. As it's using the windows api making it part of the core of NxCommonRun isn't a good idea because it breaks the pure vcl (and I like that very much btw). I wrote it especially the way it is so i would have to change the rest of the NextSuite for a feature I liked having myself and was fun to write. It links to a component and not the other way round (as it would not work on other vcl's like plain TEdit's anymore).

Beware it's a tricky windows api you're tapping into that might not be that portable between operating systems (I tested it on winxp pro only). Thats the reason why i think it should remain in a separate package and not linked hard into the rest of the suite.

Autocompletion will never be easy on a grid as you probably want it on some columns only and perhaps different between column. So you'll end up with either a bunch of autocompletions or just add the code (a few lines) and have a single one that is working as it should. Autocompletion cannot work on the grid, it can only work on the editor when it's visible. And because it only exists during the editing cycle linking a grid to autocompletion makes no sense.

Personally I cannot see a reason to sacrifice pure vcl for the sake of not having to add those few lines (where these lines will be necessary very soon anyway). Bottom line: if you like the AutoCompletion component, just add the lines to the grid and you'll notice that it's more powerfull that way.

[Marc]

ok

I'm trying to put a NXAutocomplete with my DBGrid as shown in tutorial web page.

It works fine, but when I enter characters Tab cannot be use to exit the edited column. Without autocomplete, TAB character has good comportement and cursor switch to next input control

[emailaya]

is there a chance that autocompletion wont work under old windows
like me, 2000 etc?

[Marc]

is there a chance that autocompletion wont work under old windows
like me, 2000 etc?

TAB key don't work with Autocomplete linked to a inplace dbgrid combobox

[Boki (Berg)]

Hello Marc,

There are 2 possibilities:

1) When WantTabs is set to True, next item in TNxAutoCompletion popup will be selected.
2) When WantTabs is set to False, next control will be selected as usuall.

regards

[wvd_vegt]

Hi,

I'm trying to put a NXAutocomplete with my DBGrid as shown in tutorial web page.

It works fine, but when I enter characters Tab cannot be use to exit the edited column. Without autocomplete, TAB character has good comportement and cursor switch to next input control

In the autocomplete stuff there is no character passed, so there is no way to fix behaviour like this other than workaround. The api says once a selection is made the control should behave like it's typed in by the user (but hey it's microsoft doing a promise for their own controls).

You might try to add aoUseTab to TnxAcOption and add ACO_USETAB Options in TnxAutoCompletion.Setup, recompile and see what it does. A number of IAutoComplete2 options are not made public.

Let me know what it does.

[Marc]

Hi,
In the autocomplete stuff there is no character passed, so there is no way to fix behaviour like this other than workaround. The api says once a selection is made the control should behave like it's typed in by the user (but hey it's microsoft doing a promise for their own controls).

You might try to add aoUseTab to TnxAcOption and add ACO_USETAB Options in TnxAutoCompletion.Setup, recompile and see what it does. A number of IAutoComplete2 options are not made public.

Let me know what it does.

It doesn't work

[wvd_vegt]

Hi,

It doesn't work

I was afraid of that. I'll make the option public anyway (as it will not harm).

[Marc]

Hi,
I was afraid of that.

me too