NT8 manual -> Beast Practices -> Responding to user events question

[fx.practic]

Please, look at screenshot.
Why methods have different names?
Is this mistake, or there is some logic behind this?

[NinjaTrader_Jesse]

Hello,

Thank you for the post.

In this example, there are Two events being subscribed/unsubscribed (two different objects with the same event type). Generally, each event handler would have its own void method to receive the event arguments when the event happens.

Because the Event Args are likely different between events and they are not interchangeable each would require the specific void method with the correct overload parameters.

In this specific example, the EventArgs happen to be the same but it would be best practice to have two separate method bodies so you know what void is executing the code for which mouse down event.

I look forward to being of further assistance.

[fx.practic]

Oh, I'm sorry Jesse, for vague question.

I mean why
doCustomWPFControlClickEvent differ form DoCustomWPFControlClickEvent

and

doUserClickedChartPanelEvent differ form DoUserClickedChartPanelEvent

I mean difference in first letter: big and small letter "D".

[NinjaTrader_Jesse]

Hello,

This is likely just the original author of this sample has just left one as a lower case, you can name a Method any way you would like so long as it is a valid name for a method.

Please let me know if I may be of further assistance.