I use a delegate pattern to do this very thing. Its really the only
way to keep presenter logic where it belongs without polluting your
namespace with widgets. The SuggestBox is none the wiser. Just make
sure your delegator handles the base case where its delegate oracle is
null, of course, othe
Thats a good idea, I will look into doing that instead.
The SuggestBox isn't going to have any problems with the SuggestOracle
being changed even though, if implemented this way, it doesn't know it
is being changed?
Thanks again,
Pat
On Jan 6, 11:46 am, Thomas Broyer wrote:
> How about having a
I have a form that depending upon a listbox value that the user
selects needs different suggestions.
Currently I have 1 SuggestOracle and I have to clear it and reload it,
with values from the server, every time the user changes the ListBox.
What I would like to do is store a SuggestOracle for eac
