C#

dan neely wrote:

How does this work if buggy code results in the same handler being registered twice?

private int clicks=0;
private int handlers=0;
Button btn=new Button();

public override void Run(int arg) {
    doClick();
    addHandler();
    doClick();
    addHandler();
    doClick();
    removeHandler();
    doClick();
    removeHandler();
    doClick();
    removeHandler();
    doClick();
}

void doClick() {
    log("CLICK");
    btn.PerformClick();
}

void addHandler() {
    handlers++;
    log("ADD HANDLER "+handlers);
    btn.Click+=new EventHandler(btn_Click);
}

void removeHandler() {
    log("REMOVE HANDLER "+handlers);
    handlers--;
    try {btn.Click-=new EventHandler(btn_Click);
    } catch { log("failed to remove handler"); }
}

void btn_Click(object sender, EventArgs e) {
    clicks++;
    log("  got click "+clicks);
}

15.109     CLICK
15.125     ADD HANDLER 1
15.140     CLICK
15.156       got click 1
15.203     ADD HANDLER 2
15.218     CLICK
15.296       got click 2
15.312       got click 3
15.328     REMOVE HANDLER 2
15.343     CLICK
15.343       got click 4
15.437     REMOVE HANDLER 1
15.468     CLICK
15.484     REMOVE HANDLER 0
15.593     CLICK

Luc Pattyn wrote:

The magic is you create a new object to remove an old (but very similar) object !

Martin# wrote:

This was my Nr.:1000 post

Luc Pattyn wrote:

Aha, that explains a few things. Now take that holiday !

[HKEY_LOCAL_MACHINE\SYSTEM\CURRENTCONTROLSET\CONTROL\FileSystem\Ntfs]
"Disable8dot3NameCreation"=dword:1