PC Review
Forums
Newsgroups
Microsoft DotNet
Microsoft VB .NET
Cmd Button Click event not executed
Forums
Newsgroups
Microsoft DotNet
Microsoft VB .NET
Cmd Button Click event not executed
![]() |
Cmd Button Click event not executed |
|
|
Thread Tools | Rate Thread |
|
|
#1 |
|
Guest
Posts: n/a
|
Hey folks
I have some interesting behaviour going in. Inside a form, I download some data. The form is used to show the status, and set button states etc... I have a break point set up at one of the button click event handlers. When the button is clicked, the application doesn't stop at the breakpoint for the click event. Nor does it stop at any of the other breakpoints. The strange thing is that the code seems to execute, the button states change accordingly and then the form closes. I have breakpoints setup where the button states get changed. They don't seem to work either.Although before I get to that point they do work. I am starting this process using a timer so that I can start the process after the form loads. I'm wondering if somehow the timer (which I think is executed on a seperate thread) is somehow messing things up. VB.Net + VS.Net 2003 Any ideas on this one? thanks folks LDD |
|
|
|
#2 |
|
Guest
Posts: n/a
|
"LDD" <largedoubledouble@gmail.com> schrieb
> Hey folks > > I have some interesting behaviour going in. > > Inside a form, I download some data. The form is used to show the > status, and set button states etc... > > I have a break point set up at one of the button click event > handlers. When the button is clicked, the application doesn't stop > at the breakpoint for the click event. Nor does it stop at any of > the other breakpoints. Switched to Release configuration? Armin |
|
|
|
#3 |
|
Guest
Posts: n/a
|
I haven't switched to release.
The method to change the state of the buttons gets called a few times during the download. The breakpoints are functional prior to me pressing the abort button. When the abort button is pressed, the button states change and the window is supposed to stay open. And the breakpoints should halt the application. What does happen is that the states change, and the form closes. So the code where the breakpoints are seem to be executing. LDD "Armin Zingler" <az.nospam@freenet.de> wrote in message news:Oq8MCujBGHA.640@TK2MSFTNGP10.phx.gbl... > "LDD" <largedoubledouble@gmail.com> schrieb > > Hey folks > > > > I have some interesting behaviour going in. > > > > Inside a form, I download some data. The form is used to show the > > status, and set button states etc... > > > > I have a break point set up at one of the button click event > > handlers. When the button is clicked, the application doesn't stop > > at the breakpoint for the click event. Nor does it stop at any of > > the other breakpoints. > > Switched to Release configuration? > > > Armin |
|
|
|
#4 |
|
Guest
Posts: n/a
|
"LDD" <largedoubledouble@gmail.com> schrieb
> I haven't switched to release. > > The method to change the state of the buttons gets called a few > times during the download. > The breakpoints are functional prior to me pressing the abort > button. When the abort button is pressed, the button states change > and the window is supposed to stay open. And the breakpoints should > halt the application. > > What does happen is that the states change, and the form closes. So > the code where the breakpoints are seem to be executing. If you don't "start without debugging" I don' know why the breakpoints are not hit. Somebody once used Ctrl+F5 to do a full compile like in VB6, but this is now starting without attaching the debugger. Maybe you did this, too, otherwise, sorry, I can't help here. Armin |
|
![]() |
|
| Thread Tools | |
| Rate This Thread | |
|
|

Main Page 

