How to Add an eventHandler only one time?

[aplaxas]

Hi!

"CDemo.Call " eventHandler is added to "button3.cl ick"
Event when both button1 and button2 are clicked.
However, I want to add "cd.Call" only one time even though
I clicked both button1 and button2.

For Example,
1. Click button1
2. Click button2
3. Click button3
4. One MessageBox is shown

How to do this job?
private System.Windows. Forms.Button button1;
private System.Windows. Forms.Button button2;
private System.Windows. Forms.Button button3;

public CDemo cd = new CDemo();
..
private void button1_Click(o bject sender, System.EventArg s
e)
{
button3.Click += new EventHandler(cd .Call);
}

private void button2_Click(o bject sender, System.EventArg s
e)
{
button3.Click += new EventHandler(cd .Call);
}

..
..
..
public class CDemo
{
public void Call(object sender, System.EventArg s e)
{
MessageBox.Show ("Demo");
}
}

[Mattias Sjögren]

private bool handlerAdded = false;

private void button1_Click(o bject sender, System.EventArg s e)
{
if ( !handlerAdded ) {
button3.Click += new EventHandler(cd .Call);
handlerAdded = true;
}
}

and similarly for button2_Click.

Mattias

--
Mattias Sjögren [MVP] mattias @ mvps.org
http://www.msjogren.net/dotnet/ | http://www.dotnetinterop.com
Please reply only to the newsgroup.

[Jongmin]

Hi!

Even your code provides one solution, I can't use your
code.
I don't want use another global variable in order to solve
this situation.
I have to solve this problem only with both object
instance button3 and cd.

Thanks,
Jongmin

-----Original Message-----

private bool handlerAdded = false;

private void button1_Click(o bject sender, System.EventArg s e){
if ( !handlerAdded ) {
button3.Click += new EventHandler(cd .Call);
handlerAdded = true;
}
}

and similarly for button2_Click.

Mattias

--
Mattias Sjögren [MVP] mattias @ mvps.org
http://www.msjogren.net/dotnet/ | http://www.dotnetinterop.comPlease reply only to the newsgroup.
.

[lukasz]

how about this:

private void button1_Click(. ..) {
button3.Click -= new EventHandler(cd .Call);
button3.Click += new EventHandler(cd .Call);
}

private void button2_Click(. ..) {
button3.Click -= new EventHandler(cd .Call);
button3.Click += new EventHandler(cd .Call);
}

Keeps only one event handler.

[Marcin Grzębski]

Hi,

Why don't you enable button3 on button1 (or button2) click?
Has it any more functionality than cd.Call?

<snip>

I don't want use another global variable in order to solve
this situation.

If code of your button handlers lies in a form class,
you shold not affraid to use any simple variables. They take
less memory than any of your control.

Previous solutions should be suitable too.

Regards

Marcin

[Jongmin]

The codesnippet just simplified my problem for explaining.

In real code, I have many kinds of object not window form
types.

-----Original Message-----
Hi,

Why don't you enable button3 on button1 (or button2) click?Has it any more functionality than cd.Call?

<snip>

I don't want use another global variable in order to solve this situation.
If code of your button handlers lies in a form class,
you shold not affraid to use any simple variables. They

takeless memory than any of your control.

Previous solutions should be suitable too.

Regards

Marcin
.

[Jongmin]

Yes, I have used your way as the following code.

for(int intI=0; intI < 10; intI++)
button3.Click -= new EventHandler(cd .Call);

button3.Click += new EventHandler(cd .Call);

I thought this is so clumsy.

-----Original Message-----
how about this:

private void button1_Click(. ..) {
button3.Click -= new EventHandler(cd .Call);
button3.Click += new EventHandler(cd .Call);
}

private void button2_Click(. ..) {
button3.Click -= new EventHandler(cd .Call);
button3.Click += new EventHandler(cd .Call);
}

Keeps only one event handler.
.

[lukasz]

Can you explain why you want such a strange behavior? Maybe you have wrong
approach to the problem.
Uzytkownik "Jongmin" <an*******@disc ussions.microso ft.com> napisal w
wiadomosci news:4c******** *************** *****@phx.gbl.. .

Yes, I have used your way as the following code.

for(int intI=0; intI < 10; intI++)
button3.Click -= new EventHandler(cd .Call);

button3.Click += new EventHandler(cd .Call);

I thought this is so clumsy.

-----Original Message-----
how about this:

private void button1_Click(. ..) {
button3.Click -= new EventHandler(cd .Call);
button3.Click += new EventHandler(cd .Call);
}

private void button2_Click(. ..) {
button3.Click -= new EventHandler(cd .Call);
button3.Click += new EventHandler(cd .Call);
}

Keeps only one event handler.
.

[Jongmin]

Basically, I have four classes related to this situation,
TPart, TRefPart, TPartCollection , and TRefPartCollect ion.
TPart is basic type and holds data.
TRefPart is referring TPart instance. It means TRefPart
depends on TPart.
TPartCollection and TRefPartCollect ion is used for
DataBinding.

For Example,

TPart part = new TPart();
part.Idx = 1;
part.Name = "Hard Disk XXXXXXX";

TRefPart refPart1 = new TRefPart(part);
TRefPart refPart2 = new TRefPart();
refPart2.Idx = part.Idx;

TRefPartCollect ion refParts = new TRefPartCollect ion();
refParts.Add(re fPart1);
refParts.Add(re fpart2);

listBox.DataSou rce = refParts;
part.Name = "Hard Disk";
MessageBox.Show (refPart1); // -> "Hard Disk";
MessageBox.Show (refPart2); // -> "Hard Disk";

Even though both refPart1 and refPart2 show correct Name
of part1, this part.Name change can't refresh list of
ListBox fully, because refPart2's OnName_Changed
eventhandler is not added to Part's NameChange Event.

I have to add the following code after creating part2.
part.NameChange d = refPart2.OnName _Changed

My problem is this adding job takes places multifully at
differet area.

Thanks,
Jongmin


public class TPart
{
public event EventHandler NameChanged;

private int _Idx = 0;
public virtual int Idx
{
set { _Idx = value;}
get { return _Idx ;}
}

private string _Name = "Noname";
public string Name
{
set
{
_Name = value;
Name_Changed();

}
get { return _Name ;}
}
private void Name_Changed()
{
if (NameChanged != null)
NameChanged(thi s, System.EventArg s.Empty);
}
}
public class TRefPart
{
public event EventHandler NameChanged;

public TRefPart()
{
}

public TRefPart(TPart part)
{
this.Idx = part.Idx;
ConnectEventHan dler(part);
}

public static TPart operator ~(TRefPart a)
{
/*
return the TPart which has same Idx in my
application.
*/
return null;
}

public string Name
{
get
{
if ((~this) != null)
return (~this).Name;
else
return "N/A";
}
}
private void ConnectEventHan dler(TPart part)
{
if (part != null)
{
part.NameChange d +=new EventHandler
(OnName_Changed );
}

}
private void DisconnectEvent Handler(TPart part)
{
if (part != null)
{
part.NameChange d -=new EventHandler
(OnName_Changed );
}
}

public override string ToString()
{
return Name;
}

public void OnName_Changed( object sender,
System.EventArg s e)
{
base.Name_Chang ed();
}
}

public class TRefPartCollect ion :CollectionBase ,
IBindingList
{
public TPartCollection ()
{
}

private ListChangedEven tArgs resetEvent = new
ListChangedEven tArgs(ListChang edType.Reset, -1);
public event ListChangedEven tHandler ListChanged;
public event EventHandler RefPartAdded;
public event EventHandler RefPartRemoved;

..
..

protected override void OnInsertComplet e(int index,
object value)
{
RefPart_Added(( TRefPart)value) ;
OnListChanged(n ew ListChangedEven tArgs
(ListChangedTyp e.ItemAdded, index));
}

private void RefPart_Added(T RefPart item)
{
item.NameChange d += new EventHandler
(OnRefPartName_ Changed);
}

private void OnRefPartName_C hanged(object sender,
System.EventArg s e)
{
OnListChanged(r esetEvent);
}
}

public class TPartCollection :CollectionBase , IBindingList
{
public TPartCollection ()
{
}

private ListChangedEven tArgs resetEvent = new
ListChangedEven tArgs(ListChang edType.Reset, -1);
public event ListChangedEven tHandler ListChanged;
public event EventHandler PartAdded;
public event EventHandler PartRemoved;

}

[lukasz]

> TRefPart refPart1 = new TRefPart(part);

TRefPart refPart2 = new TRefPart();
refPart2.Idx = part.Idx;

Why not create refPart2 the same way as refPart1? If you have part.Idx, you
have part, so you can assign part's OnNameChanged.

Another option would be looking up the part object in TPartCollection and
once you get it, assign its OnNameChanged, all inside TRefPart.Idx setter.

public void OnName_Changed( object sender,
System.EventArg s e)
{
base.Name_Chang ed();
}

what's the base? Object?

Btw, what you present now is a bit different from what you asked about
previously.