While(true)Appl ication.DoEvent s V Application.Run

[foldface]

Hi
I am doing drag and drop between controls (listview and
treeview) using mouse_event.
What I am after is a book/resource to explain the behaviour
below.

If I do the various Win32 api calls and call Application.Run , it
works. I can see dragging and dropping on the screen.
If I do this:

while(true)
{
Application.DoE vents()
}

it works, while if I do this:

while(true)
{
FormFinder finder = new FormFinder();
FormCollection theForms = finder.FindAll( "Employee Transfers");
if(theForms.Cou nt > 0) break;
Application.DoE vents()
}

it doesn't work. The code is NUintForms b.t.w.
Its almost as if theres a timing issue involved, you have to be looking
at the queue at the right minute?

Any advice?

Thanks
F

[Jon Skeet [C# MVP]]

<fo******@yahoo .co.uk> wrote:

I am doing drag and drop between controls (listview and
treeview) using mouse_event.
What I am after is a book/resource to explain the behaviour
below.

If I do the various Win32 api calls and call Application.Run , it
works. I can see dragging and dropping on the screen.
If I do this:

while(true)
{
Application.DoE vents()
}

it works, while if I do this:

while(true)
{
FormFinder finder = new FormFinder();
FormCollection theForms = finder.FindAll( "Employee Transfers");
if(theForms.Cou nt > 0) break;
Application.DoE vents()
}

it doesn't work. The code is NUintForms b.t.w.
Its almost as if theres a timing issue involved, you have to be looking
at the queue at the right minute?

Any advice?

Application.Run is a much nicer way of handling things, I think.
Certainly a tight loop on Application.DoE vents is a bad idea.

Shouldn't your test be

if (theForms.Count == 0) break;

though - so you stop processing events when all forms have been closed,
rather than when none of them have been closed?

--
Jon Skeet - <sk***@pobox.co m>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

[foldface]

I'm waiting for a form to appear, hence the code.
I'm trying to use DoEvent to keep to the structure of NUnitForms. Is
there a way of exiting the Application.Run once its running?

I would like to know how the internals work?

[Jon Skeet [C# MVP]]

<fo******@yahoo .co.uk> wrote:

I'm waiting for a form to appear, hence the code.
I'm trying to use DoEvent to keep to the structure of NUnitForms. Is
there a way of exiting the Application.Run once its running?
It stops when the form which is passed to it is closed.
I would like to know how the internals work?

I can't help you there, although others no doubt can.

It feels like a bad idea to manually call the message pump like this.

--
Jon Skeet - <sk***@pobox.co m>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

[Sean Hederman]

As far as I can see, Application.Run kicks off a non-modal message loop, and
as Jon says will carry on running until the form is closed.
Application.DoE vents also kicks off a message loop (actually the same one as
Run), however since no form is set for this message loop it won't exit the
loop when the form is closed, but rather once the message pump has been
emptied.

When dealing with forms, it is much better to rely on the Framework to
handle the messaging for you (via Form.Show, Form.ShowDialog &
Application.Run ) unless you have a really deep understanding of the windows
message pump.

<fo******@yahoo .co.uk> wrote in message
news:11******** *************@z 14g2000cwz.goog legroups.com...

I'm waiting for a form to appear, hence the code.
I'm trying to use DoEvent to keep to the structure of NUnitForms. Is
there a way of exiting the Application.Run once its running?

I would like to know how the internals work?

[foldface]

> When dealing with forms, it is much better to rely on the Framework
to

handle the messaging for you (via Form.Show, Form.ShowDialog &
Application.Run ) unless you have a really deep understanding of the windows message pump.

This is purely for testing using NUnit. NUnitForms seems to rely on
Application.DoE vents and I was trying to work with that. Instead
I'm now doing something like

[Test]
public void Test1()
{
// make my form, etc
Thread thread = new Thread(new ThreadStart(Oth erMethod));
thread.Start();
Application.Run ()
}

public void OtherMethod()
{
// wait for a bit, do some stuff with the forms
Application.Exi t()
}

repeat for other tests.

but this is the best I've come up with rather than 'the' way to do it.
It would
be nice to have a real understanding of how DoEvents and Run works so
that
I have the option of doing it anyway I want. Also I just like knowing
how things work.

Ta
F

[Sean Hederman]

I'd spelunk them with Reflector to find out the nitty-gritty's, but my
earlier post gave the gist of it. The message loop is fairly simple:
1. Call PeekMessage to get messages for current thread. If there aren't any
and it's not a form loop then exit out of the loop
2. Call GetMessage on the current thread, and create a Message object from
it.
3. If it's a control, call PreProcessMessa ge on it, jumping to 6 if the
message was handled.
4. Translate virtual key codes messages to character messages
5. Dispatch the message to it's target
6. If this is for a form, and it's not closing, back to 1

(I've simplified it a bit, but you get the idea)

As I said before, DoEvents executes this procedure without a specific form,
Run(Form) the indicated form, and ShowDialog(Form ) runs it with various
modal options set.

<fo******@yahoo .co.uk> wrote in message
news:11******** **************@ o13g2000cwo.goo glegroups.com.. .

When dealing with forms, it is much better to rely on the Framework

to

handle the messaging for you (via Form.Show, Form.ShowDialog &
Application.Run ) unless you have a really deep understanding of the

windows

message pump.

This is purely for testing using NUnit. NUnitForms seems to rely on
Application.DoE vents and I was trying to work with that. Instead
I'm now doing something like

[Test]
public void Test1()
{
// make my form, etc
Thread thread = new Thread(new ThreadStart(Oth erMethod));
thread.Start();
Application.Run ()
}

public void OtherMethod()
{
// wait for a bit, do some stuff with the forms
Application.Exi t()
}

repeat for other tests.

but this is the best I've come up with rather than 'the' way to do it.
It would
be nice to have a real understanding of how DoEvents and Run works so
that
I have the option of doing it anyway I want. Also I just like knowing
how things work.

Ta
F