Where is a control's parameter list documented?

  • Thread starter Thread starter HillBilly
  • Start date Start date
H

HillBilly

One question I have not figured out is how to learn which event parameter
list is supported by a control? EventArgs, CommandEventArgs, what?
 
One question I have not figured out is how to learn which event parameter
list is supported by a control? EventArgs, CommandEventArgs, what?

I'm not sure I understand your question. I don't think the list of
all event parameters used by a control is a useful thing to know.

A control raises some number of events. When the handler for an event
is called, an event parameter is passed. Each event has a specific
parameter type.

If you want to know which parameter a specific event uses, you can
either look it up in the documentation, or code the parameter as
something clearly illegal like 'string' and the compiler error message
will tell you what is expected (unless you are using VB with OPTION
STRICT OFF, in which case you need to bit the bullet and change to
OPTION STRICT ON).
 
Jack Jackson said:
I'm not sure I understand your question. I don't think the list of
all event parameters used by a control is a useful thing to know.

A control raises some number of events. When the handler for an event
is called, an event parameter is passed. Each event has a specific
parameter type.

If you want to know which parameter a specific event uses, you can
either look it up in the documentation, or code the parameter as
something clearly illegal like 'string' and the compiler error message
will tell you what is expected (unless you are using VB with OPTION
STRICT OFF, in which case you need to bit the bullet and change to
OPTION STRICT ON).

Looking --it-- up in documentation is the task I'm trying to determine Jack.
Here and there I see a parameter list mentioned in he documentation; not
clearly identified as such and then not consistently as every event of every
method appears to support at least two parameters. Since there are different
parameter names and types I've remained uninformed and have relied on
Intellisense to give me some kind of clue but not much can be inferred from
Intellisense.

It would be very useful IMO if this context of passing arguments using
parameters were documented better as clearly the construct is fundamental to
the method or it would not be used at all so why not then expound on the
scope of the types we may only infer by reading some arbitrary name; and an
arbitrary name that does not lead anywhere specific in the current
documentation as my meager attempts to find have failed to produce in any
circumstance but accidently.
 
Looking --it-- up in documentation is the task I'm trying to determine Jack.
Here and there I see a parameter list mentioned in he documentation; not
clearly identified as such and then not consistently as every event of every
method appears to support at least two parameters. Since there are different
parameter names and types I've remained uninformed and have relied on
Intellisense to give me some kind of clue but not much can be inferred from
Intellisense.

It would be very useful IMO if this context of passing arguments using
parameters were documented better as clearly the construct is fundamental to
the method or it would not be used at all so why not then expound on the
scope of the types we may only infer by reading some arbitrary name; and an
arbitrary name that does not lead anywhere specific in the current
documentation as my meager attempts to find have failed to produce in any
circumstance but accidently.

Sorry, I don't understand what the problem is. Can you give an
example?
 
Jack Jackson said:
Sorry, I don't understand what the problem is. Can you give an
example?

Noting I'm still trying to make sense of delegates and events I refer to the
earlier examples I mentioned such as EventArgs, CommandEventArgs and the
many other such "type" I see used with the actual parameter e.
 
Back
Top