Does the "System.EventArgs" create an infinite loop of the object "Empty"?

Question

0.00/5 (No votes)

See more:

I'm having an event on my ContextMenu which have the "System.EventArgs" as a parameter

The event procedure looks like this:

VB

Private Sub CMRoot_ItemClicked(Sender As Object, e As System.EventArgs) Handles CMRoot.ItemClicked

It seems the "e" object is populated with an infinite loop of the object "Empty".
screen dump
Is this something I should be worried about?

Posted 1-Jul-14 23:09pm

Member 4627922

Updated 1-Jul-14 23:21pm

v4

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Kim Togo · Accepted Answer · 2014-07-02T00:12:00

Solution 1

Short answer, no.

Long answer.
The reason is that System.EventArgs.Empty[^] is a Static field, that gives an Empty EventArgs and when you then in debugger goes in that static field, it will give you a new Empty EventArgs, and a new one and an new etc.

Posted 2-Jul-14 0:12am

Kim Togo

Updated 2-Jul-14 0:13am

v2