debounce functionality added. Closes: #58

[abdullah2993]

Ability to debounce the events added.
Closes: #58

[radovskyb]

Hi @abdullah2993,

May I ask how this is different than just setting a higher polling time instead of the default 100ms? :)

[abdullah2993]

@radovskyb This will be a little hard to explain but let me try. Imagine if you change 20 files and save them, the command will be executed 20 times, you can find a much better explained scenario here. With this feature you can delay the execution of the command for a specified time and consume the file change events during that period and execute the command only once. So if 20 files are changed in a very close proximity of each other the command will only be executed once.

[progrium]

Yeah, you can roughly get this from the SetMaxEvents feature assuming your filters are set up correctly to only catch actionable events. IMO debouncing isn't necessary here and if you really need it there are libraries and very short snippets to add your own debouncer.