Form programmer chooses which tangy-location input is used for the visits tab in a form

[esurface]

On the offline client, the 'Visits' tab shows a count of forms by location and date to help data collectors review where and when forms were filled. The location associated with the form is based on the first tangy-location input in that form ('noLocation' if there is no tangy-location input). This is not useful if the form programmer wants to have a different location list than the first to be used as the location in the visits tab. An improvement will to to add a setting in tangy-location-editor that allows the form programmer to choose which location list to use.

Caveats --- the tangy-form-editor elements are not currently aware of each other. The addition of a cross-input setting is new. There should only be one tangy-location selected per form. Best attempt might be to leave them unaware of each other. If the form programmer selects more than one location for the visit tab, then the code will use the first one.

Related to: #3628