Should this feature be enabled at the device level for all questions or something that a form designer enables on particular questions.
I would lean toward the latter. Doing the former might be disruptive to existing users and could even lead to errors. Some questions you probably want people answering fresh from their head, not from an existing value.
Is there a limit to how many things are remembered? If so, how does that get configured?
Could be an option I guess. In our case we only need the last one.
Is there a need to pre-load the auto-complete list?
Not sure what this means.
How does one remove an item from this list?
This seems like it would be rarely needed. But I guess maybe you have little x's on each list item?
Do deleted or cleared answers also appear on the list?
I would say no.
Does deleting the form that generated the item also delete it from the list?
It might be interesting to be able to specify a unique identifier for a question and use that as the lookup key for these answers. That way if you have the same question (e.g. what is the village number) on multiple forms, you could re-use the value across both. If not provided then it would default to each question being treated separately.
If we did this, then the answer to the above is likely 'no'.
Does this list appear immediately or as you start to type?
I think this needs to be an option. Again, in our case, we want the immediate last value to be pre-loaded as the default. And in some cases we even want to increment it.
Also, by immediately, do you mean 'on focus'? Because in a field-list group it would be weird to show a bunch at once.
So some options might be:
- lookup-key (string)
- max-items (integer)
- list-appear (on-focus, on-type, none)
- pre-fill-last (true, increment, false)
Note that all the above reasoning applies to open text or number fields.
I note some of the above requests talk about basically re-sorting recently used values in a select1 or select question to the top of the list (right?). Perhaps lookup-key and max-items would apply in those cases but not the other two.
It also might be a good idea to track this as a separate feature request as it's rather different than the open text field case. Perhaps some of the same backend machinery could be used...