Extract clench from orgasm_control_updateArousal #87
Conversation
…function returning clench time and publishing EVT_ORGASM_START event at orgasm threshold
There was a problem hiding this comment.
This is excellent! Perfect!
this cleans up a huge block of code from the update_arousal call, I am all for this.
I just recently pushed a change that fixed the camelCase names from the old C++ API, so if you can just make sure that's pulled in here, this is good.
Once I fully decide how I want to extract these modes into plugins, this function can be copied to its final home, but for now even just keeping it in its own function within orgasm_control.c is a huge help to me, thanks for this.
Also, publishing the event is excellent, people have asked for arousal detection to continue during manual mode.
|
The branch is in sync with your main |
|
Btw, i'm sure you know.but the new event handler broke acces to the mercury-1000 |
Extract clench from orgasm_control_updateArousal and make it a simple function returning clench time and publishing EVT_ORGASM_START event at orgasm threshold
Take it if you think it's going in the direction you want. I know very well the clench detector and wanted to help in separating it from you updateArousal function.
It's simplified and now generates an orgasm event in your new event handler no matter what mode it's running in. Even in Manual.