That “time stamper class” is the class that recognizes input. Or senses, whatever way you want to put it.
If I wanted to consolidate timestamping functionality and didn’t care about leaving what timestamping method the user wants to use, I would’ve done so. The clock node in that post is serving as a class to hook up to, just as a example.
Personally, I think doing it that way isn’t appropriate because I don’t think systems that serve as modules (my input system in this case) should have its user go poke around in the code just to change what kind of timestamping method it’d use. Having it in that way also means you couldn’t apply separate timestamping methods on 2 InputSensor instances serving as a input action map because it’d be hardcoded to only use logic taken out of the clock class, which doesn’t allow the user to set it to whatever they want.
Look, I sense you’re suspicious of me, which I would bet it’s possibly due to some kind of discrepancy between that code block I provided in my OP and me not knowing how to access a function from another node via a string name. I’ve read exactly the part where you said from another post:
I understand the sentiment and I can agree with this conclusion. However, I can’t learn what I don’t know if you play coy as you stated; because I won’t know what you’re thinking until you elaborate:
We could probably move to direct messages, seeing as this topic is already solved.