Basically, yes. What I do is iterate over all the children in the current view (myModule.getChildren). Depending on the type of object, I run different code. For example, if the object is a datagrid I grab the dataprovider and search that. If it's a text field, it is way easier. It can get tricky in some situations (like the data is filtered etc). Then, of course, you need a way to highlight the found text.
--- In [email protected], Baz <li...@...> wrote: > > Does the search functionality have to be customized for the different > elements and states currently on the screen, or is there a way to generalize > it for any/all visible text? For example if you have an About Us page with > one big text block, it takes different code to search that over the Search > Results page which has an itemrenderer composed of multiple labels. > > Cheers. > > On Tue, May 25, 2010 at 6:01 AM, valdhor <valdhorli...@...>wrote: > > > > > > > Yes, openSearchWindow() is my own custom "find" functionality coded in flex > > and manually searches contents on the page. > > > > The browsers search box is part of the browser that has no knowledge of the > > contents of the Flash plug-in. > > > > I also had a different project that has a menu bar system at the top and a > > text field for searching. I set up the CTRL+F listener to set focus to that > > text field. It made it look kinda like the browsers search box (Enough so > > that the users didn't complain). > > > > > > --- In [email protected] <flexcoders%40yahoogroups.com>, Baz > > <lists@> wrote: > > > > > > I love it. So openSearchWindow() is your own custom "find" functionality > > > coded in flex and manually searches contents on the page, right? You > > haven't > > > found a way to integrate directly with a browser's search box? > > > > > > Baz > > > > > > > > > On Mon, May 24, 2010 at 10:48 AM, valdhor <valdhorlists@>wrote: > > > > > > > openSearchWindow(); > > > > > > > > > >
