No, because when the Click event is generated, the DoubleClick event has not
yet occurred.  

There are two ways to handle this issue:

Option 1:  The preferred way is to ensure that your single/double click
responses are complimentary.  Like in Windows Explorer, a single click
selects an item, a double click launches it.  That way you can monitor and
handle the Click/DoubleClick events individually without worrying about the
other event.

Option 2:  If you definitely do not want your single click response to
execute if the user double-clicks, your only option is to launch a timer
after the first click, wait the double-click time
(SystemInformation.DoubleClickTime), and if a second click does not occur,
your timer will execute the response to the first click.  The downside to
this option is that your program will seem to lag single clicks by about a
half-second while it waits to see if the second click will occur.