Stupid question - custom events/functions that we create are referred to as LogEvents (in the custom stub files that are generated, in the TestHarness - even in the docs) - but why?
Is the "Log" prefix a holdover from some original functionality...or?
Just curious.
Best Answer
C
Customer Support
said
over 2 years ago
Good question Jeff.
The answer is that we cant really remember. There was a reason that spans back to the initial platform concept.
It comes from the idea of the device Logging an Event with GameSparks.
Sean
1 Comment
Customer Support
said
over 2 years ago
Answer
Good question Jeff.
The answer is that we cant really remember. There was a reason that spans back to the initial platform concept.
It comes from the idea of the device Logging an Event with GameSparks.
Jeff Amiel
Stupid question - custom events/functions that we create are referred to as LogEvents (in the custom stub files that are generated, in the TestHarness - even in the docs) - but why?
Is the "Log" prefix a holdover from some original functionality...or?
Just curious.
Good question Jeff.
The answer is that we cant really remember. There was a reason that spans back to the initial platform concept.
It comes from the idea of the device Logging an Event with GameSparks.
Sean
Customer Support
Good question Jeff.
The answer is that we cant really remember. There was a reason that spans back to the initial platform concept.
It comes from the idea of the device Logging an Event with GameSparks.
Sean
-
Documentation Notes
-
Design issues with user events
-
Using NoSQL
-
Runtime Collections vs Metadata Collections
-
Anonymous authentication from browser app
-
Modules
-
Movement With Unity
-
Problem with url parameters for downloadables
-
Querying NoSql GameSparks database
-
Challenge accesType
See all 2239 topics