Some questions/suggestions:
I know what you want to do, and i understand why, only could this not be done simpler ?

(why is it called TASK_PROCESSOR_HZ ?, maybe just call it 'schedule_resolution' or timer_resolution)

• If the default was 1 second, and the TASK_PROCESSOR_HZ = 25 now, this will now sleep 40 ms ?
• making the delay time a float is perfect
• If we make the schedule_resolution 500ms (for instance), we sleep 500ms
  subtract 500ms from the delay/counter, when the counter <=0 then... we do something
  (that should also work for a float?)
• i do not understand:
  if (m_iAcceptHardwareTimerCounter <= (1./TASK_PROCESSOR_HZ/2))

• TASK_PROCESSOR_HZ = 25 means the event system will run 25 times per second and indeed sleeps for 40ms. I thought calling it Hz immediately makes it clear how often it runs (Hz includes the timeframe, a second), but I'd be glad to change it if you prefer so.
• Comparing less then or equal does work for floats, it's just not guaranteed to be exactly zero. Hence the comparison with half an interval (1./TASK_PROCESSOR_HZ/2). This also captures situations where the float would be 0.000000001. Using half an interval puts the turning point exactly in the middle and leaves no room for rounding errors.

25 times a second ? dont you think that is a bit to much ?

That's why I've turned it into a #define, to test various frequencies :). Turns out that for my situation I need at least 10 times a second (10Hz, 100ms interval), but like I said, it makes no difference performance wise to push it a bit more. I've had it running for days at 50Hz (20ms interval) without any problems whatsoever, but that was overkill for sure.

maybe timer_resolution_hz will be read from setup->settings ?

I've thought of that too, but I came to the conclusion that it wouldn't hurt 'ordinary' users in terms of performance (or anything else for that matter) if the event system runs more frequently. They wouldn't even notice it. And for those in need of it, it is just there :) so why bother making this a setting, imho.

Nice work!
We already had some discussion about this. Nice to see someone had time to make the implementation!
Problem: actions take a full second to trigger

For me the 10 times/sec was quite good.

Sorry, i forgot to merge this ;)... Thanks for the patch