Parent of Target
bobsneidar at iotecdigital.com
Wed Aug 23 10:55:34 EDT 2017
I have that very thing. I call it searchBar. It looks pretty much like a search field from a browser or Finder window (in a somewhat earlier version of the OS) and it's designed to retrieve data and update a datagrid.
I would post the rather simple code, except it is dependent on sqlYoga and some custom functions I have. I could probably make it self contained (although it almost is now) but that has no value to me. If you are interested I can send you a stack with the custom control, and you can massage it to do what you want.
> On Aug 22, 2017, at 15:46 , Trevor DeVore via use-livecode <use-livecode at lists.runrev.com> wrote:
>> See earlier longer memo.
>> USE CASE aka "Problem to Solve"
>> is a frame work with multiple stacks/aka "modules" with content.
>> Search will be a global requirement.
>> I can identify, at least for now, three "classes" of content to be search
>> in any given context/module
> Hi BR,
> Let's see if I understand the problem sufficiently. Below you will find my
> responses. If they seem way off then assume I didn't understand the
> question :-)
> You have multiple components that are involved with a basic search UI. At
> the very least you need the following:
> 1. The UI element that the user types the search term into.
> 2. The code that processes the search term entered and fetches the search
> 3. The UI element that displays the search results.
More information about the Use-livecode