blank form when debugging

10 Mar 2006 4:55 PM

raulavi

vb VS 2003
Hi all: thanks to all in advance for your responses.
my app displays the form , then when it reaches a debbuging point the form
is blanked, (it just shows the frame around the form) I need to see the info
that should be displayed . I tried me.refresh before the debugging point.
Q: 1. when the refresh actually refreshes the form?
Q: 2. what do i need to do to see my form at debugging time? (works in
normal mode)
the code is: when click a btn, does a loop to shk the database with a
System.Threading.Thread.CurrentThread.Sleep(3000) '3sec

Thanks

10 Mar 2006 5:25 PM

Chris

raulavi wrote:
Show quoteHide quote

> vb VS 2003
> Hi all: thanks to all in advance for your responses.
> my app displays the form , then when it reaches a debbuging point the form
> is blanked, (it just shows the frame around the form) I need to see the info
> that should be displayed . I tried me.refresh before the debugging point.
> Q: 1. when the refresh actually refreshes the form?
> Q: 2. what do i need to do to see my form at debugging time? (works in
> normal mode)
> the code is: when click a btn, does a loop to shk the database with a
> System.Threading.Thread.CurrentThread.Sleep(3000) '3sec
>
> Thanks
>
>
>
>

You can not break and see then form. The form need to call the paint
event in order to display the contents, since you have stopped the
execution, then it can't refresh. You will need to find some other way
to see the contents, such as looking at the form variables or don't do a
breakpoint.

Chris

10 Mar 2006 6:32 PM

raulavi

At least...i should see what it was before stopping for debugging. correct?
why is blanked.

Show quoteHide quote

"Chris" wrote:

> raulavi wrote:
> > vb VS 2003
> > Hi all: thanks to all in advance for your responses.
> > my app displays the form , then when it reaches a debbuging point the form
> > is blanked, (it just shows the frame around the form) I need to see the info
> > that should be displayed . I tried me.refresh before the debugging point.
> > Q: 1. when the refresh actually refreshes the form?
> > Q: 2. what do i need to do to see my form at debugging time? (works in
> > normal mode)
> > the code is: when click a btn, does a loop to shk the database with a
> > System.Threading.Thread.CurrentThread.Sleep(3000) '3sec
> >
> > Thanks
> >
> >
> >
> >
>
> You can not break and see then form. The form need to call the paint
> event in order to display the contents, since you have stopped the
> execution, then it can't refresh. You will need to find some other way
> to see the contents, such as looking at the form variables or don't do a
> breakpoint.
>
> Chris
>

10 Mar 2006 8:48 PM

Armin Zingler

"raulavi" <raul***@discussions.microsoft.com> schrieb im Newsbeitrag
news:A1970DAD-DEF7-4134-BBE2-34400DADF06F@microsoft.com...
> At least...i should see what it was before stopping for debugging.
> correct?
> why is blanked.

It is blank because the program does not run if you go into debug mode. If
it does not run it also does not update the form's content.

Armin

11 Mar 2006 6:43 AM

Cerebrus

Hi Raul

> At least...i should see what it was before stopping for debugging.
> correct?
> why is blanked.

What do you want to "see" on the form ? If it is some value associated
with a control, I'm sure you can query that using the Command window.
Also, the Autos and Locals window show the values of variables in
neighbouring lines from the breakpoint.

Regards,

Cerebrus.

11 Mar 2006 10:50 AM

Armin Zingler

"Cerebrus" <zorg***@sify.com> schrieb
> Hi Raul
>
> > At least...i should see what it was before stopping for
> > debugging. correct?
> > why is blanked.
>
> What do you want to "see" on the form ? If it is some value
> associated with a control, I'm sure you can query that using the
> Command window. Also, the Autos and Locals window show the values of
> variables in neighbouring lines from the breakpoint.

I also miss it sometimes because it was different in VB6. The reason is
that, using VB6, everything was running in the same process and the VB6
IDE/runtime was actually processing the messages. This includes painting the
Form. So, breaking meant that only the interpretion of the p-code by the
IDE/runtime has stopped but not the process itself (vb6.exe) has been
interrupted. Everything was under control of the IDE and the developers
(probably) decided what is safe to do even in break mode. Painting partially
was, handling click events, for example, was not. Now, in VB.Net, there are
running two different processes, and the own application is really
interrupted by a debugger.

Armin