>
> Thx, Derrell. My plan was to pass along the "regexp" in a closure (sort
> of):
>
> b2.addListener("execute"
> , function (e) { this._search(e,"regexp");}
> , b2);
>
> What I need is a way to get at the input text field (or find a common
> parent with the element searchString, which would be cleaner).
>
At the point where you have b2, don't you also have the text field object?
Why don't you just pass it along to this._search via closure?
b2.addListener("execute"
, function (e) { this._search(e,"regexp", searchTextField);}
, b2);
Or, add it as a userdata field to b2:
b2.setUserData("searchStringObj", searchTextField);
Hmmm, I found getClass, I'll play with that. I also found getWidgetById but
> not many places -- it looks like maybe I would have to set up a registry for
> that?
I think you're making things too difficult for yourself trying to climb
hierarchies. If you ever decide to slightly modify your hierarchy, you'll
have yucky code dependencies. You're probably better off saving the
relevent information someplace that it's easily accessible.
Maintaining a registry is fine. I use the finite state machine module
qx.util.fsm.*. I like to separate gui code from functionality code, and
using the FSM makes that easy as well as providing a built-in registry.
Derrell
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
