Re: onchange for edit boxes event with WebBrowser2
- From: "Igor Tandetnik" <itandetnik@xxxxxxxx>
- Date: Sun, 18 Dec 2005 10:51:02 -0500
"Chris Berry" <chrisb@xxxxxxxxxxxxxxxx> wrote in message
news:11q9rnog4ius35@xxxxxxxxxxxxxxxxxx
> Generally that's not a problem, but at some point my user is going to
> click a toolbar button and the app needs to be able to process all the
> data in the form and can't get at it.
Why not? Just read the "value" property of each input element. You don't
need any event handlers.
--
With best wishes,
Igor Tandetnik
With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. -- RFC 1925
.
- Follow-Ups:
- Re: onchange for edit boxes event with WebBrowser2
- From: Chris Berry
- Re: onchange for edit boxes event with WebBrowser2
- References:
- onchange for edit boxes event with WebBrowser2
- From: Chris Berry
- onchange for edit boxes event with WebBrowser2
- Prev by Date: Re: onchange for edit boxes event with WebBrowser2
- Next by Date: Navigate2 on same url second time -> NavigateComplete2 does not fire
- Previous by thread: Re: onchange for edit boxes event with WebBrowser2
- Next by thread: Re: onchange for edit boxes event with WebBrowser2
- Index(es):