Note that there are some explanatory texts on larger screens.

plurals
  1. PORename ClassName_SomeEvent() handlers to SomeEventHandler()?
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COI've voted to close this question because you're looking for opinion and your own question is an opinion itself. Follow official conventions or skip them, but no answer to your question will give you a definitive argument to go your way or other.
      singulars
    2. CO@MatíasFidemraizer But the accepted question did give me a definitive argument: it can't be `OnEvent` because it's already used. Past from that, it's a matter of convention (and I agree that it wouldn't make sense to change this in a project that's already in progress with several places to refactor). Besides, my point is that the class name has no use, and there is a definitive argument that can be raised against that: give me a scenario where that class name would add value to the handler name.
      singulars
    3. COSadly I believe you didn't understand the official convention: it's not about "class name". Ok, when you handle a click in some Form, the event handler will be called "FormClassName_Click", but you forgot that **a Form is a control too**. The convention isn't "className_eventName", it's "event source identifier_eventName". You're right, class name is useless, because it's not the class name!!!!!!! It's the control ID.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload