Do you think I could just leave this part blank and it'd be okay? We're just going to replace the whole thing with a header image anyway, right?
You are not logged in.
Pages: 1
The event argument handler is commonly defined "e". PlayerIOClient.Message is an event argument handler, and so I'd look it as a default by defining it "e".
con.OnMessage += delegate (object sender, Message e) { // ... }
Yet I see many people defining Message "m". I'd like to know why this choice. I work on my projects defining Message "e".
Offline
i do this because the word message starts with m
Offline
PlayerIOClient.Message is not an event handler or "event argument handler".
Documentation: https://playerio.com/documentation/refe … ry.message
One bot to rule them all, one bot to find them. One bot to bring them all... and with this cliché blind them.
Offline
OnMessage is an EventHandler and Message is the EventArgs, which is often specified as 'e'.
*u stinky*
Offline
I generally define my exceptions using e (instead of the common ex), plus, as said by Era, "Message" starts with "m".
@Atilla
Message is an event argument (trivial description) not an EventArgs (actual Object type). Eitherway it'd obviously still start with "e".
P.S. Player.IO themselves also use "m" instead of "e".
Offline
@Atilla
Message is an event argument (trivial description) not an EventArgs (actual Object type). Eitherway it'd obviously still start with "e".
That's not a correction, it's semantics.
Player.IO doesn't always use 'm', either.
*u stinky*
Offline
Pages: 1
[ Started around 1732413396.4057 - Generated in 0.040 seconds, 12 queries executed - Memory usage: 1.44 MiB (Peak: 1.56 MiB) ]