Order of Sequence for Multiple Subroutines Handling the Same Event

[Ideas Man]

I have a couple of subroutines that all handle the same event for many controls. Is it possible to predict or force the way the program accesses each subroutine when the event is fired?

i.e.

Private Sub Sub1(...) Handles Button1.Click
...
 
Private Sub Sub2(...) Handles Button1.Click
...
 
Private Sub Sub3(...) Handles Button1.Click
...

[Webtest]

Ideas:

Pardon my ignorance (hey, I'm just a newbie!), but why do you require 3 different subroutines to handle the same event?

I know that there are things like keypress that pass through several different handlers, but these are classified as different events (key down, key up, etc.).

Use 1 handler and conditionally call your 3 subroutines from the handler in whatever order you want. ???

[Ideas Man]

Dunno, I just wanted it done that way for some reason, I know I can do it by calling different subs, maybe because not every sub handles the same controls, some are common between them, but some have their own unique controls also.

[fret]

I just wanted it done that way for some reason,

hey! just for curious thing. what are you trying to achieve anyway, i mean you said that every sub have their own unique controls but how do you like to achieve it.

[Ideas Man]

Well, I did put it in one subroutine, but it still doesn't answer the question. You must be able to do it, otherwise, why would it be possible?

[crptcblade]

It works in the order that the event handlers are added to the event. If you want to control the order, I would add the handlers manually using AddHandler.

[brown monkey]

code

Dim b As New Button()
    Private Sub Form1_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load
        b.Text = "Button1"
        AddHandler b.Click, AddressOf b_click1  ' first
        AddHandler b.Click, AddressOf b_click2  ' second    
        AddHandler b.Click, AddressOf b_click3  ' third
        Me.Controls.Add(b)
    End Sub
 
    Sub b_click1(ByVal sender As Object, ByVal e As EventArgs)
        MessageBox.Show("fist")
    End Sub
    Sub b_click2(ByVal sender As Object, ByVal e As EventArgs)
        MessageBox.Show("second")
    End Sub
    Sub b_click3(ByVal sender As Object, ByVal e As EventArgs)
        MessageBox.Show("third")
    End Sub

[taxes]

Originally posted by Ideas Man
Well, I did put it in one subroutine, but it still doesn't answer the question. You must be able to do it, otherwise, why would it be possible?

No positive answer but the firing order is NOT linked to any of:

1. The name of the event e.g. Button1_Click is not necessarily fired before Button2_Click or Button11_Click. Although altering the name of the event CAN alter the order of firing.

2. The order in which the events appear in the code.

3. The order in which the events were added to the code.

MSDN offers no advice on this.

It is possible because it cannot be diferentiated from having multiple handlers, but it is totally unnecessary, as other postings have pointed out.


Please note; The use of capitals is not intended as a "Shout" but in it's normal English usage, i.e. to draw attention to the meaning.

[Ideas Man]

Well I know that the order the code appears doesn't work, the name of the subroutine doesn't work, maybe the order it is added I'm not sure.

[taxes]

Originally posted by Ideas Man
Well I know that the order the code appears doesn't work, the name of the subroutine doesn't work, maybe the order it is added I'm not sure.

Hi,

It appears to be something to do with the name chosen for the Event but it looks like a random choice based on the name. Try naming them X1_Click; X2_Click & X3_Click. For me the call order was X3; X2; X1.

I then added (typed not copied) X4 and the new call order was X1; X3; X2; X4.

I then changed X4 to X0 and the order was X1; X0; X3; X2

I then changed X2 to Button4 and the order was X1; Button4; X0; X3.