I've just uploaded another update to SCEvents. As with the previous release (0.1.1) this one does not add any major new features but rather builds upon and improves those that were previously introduced. Version 0.1.1 introduced the ability to register paths that your client application wasn't interested in receiving events from, resulting in them being ignored. It depends how you look at it, but from my point of view the way this was implemented resulted in it having a major flaw. The flaw is in the way that SCEvents' decides whether or not it should deliver the event to the client application by testing whether the path of the event is within the array of paths that the client set to ignore. This test is done by a direct comparison of the paths which results in events from sub-directories not being ignored. This functionality that was described in my previous post now truly works whereas my previous implementation did not align with the way it was described.
In my view if I register a directory to ignore events from (that is, a directory that is a sub-directory of the paths I registered to watch) then I also want to ignore the events that originate from sub-directories
of this path. Using the example from my previous post, if I rgister my application to be notified of all all events that occur under the current user's home directory but I want to ignore those events that come from
Downloads directory then I will, but version 0.1.1 will notify my application of events from directories within the
Downloads directory. By default version 0.1.2 will also ignore these
events but because this may not always be the case, for example, your application truly does want to ignore a specific directory and doesn't care about sub-directories then there is a new option to enable or disable
this behaviour. Simply use the following method:
My thanks go to Simon Wolf for providing a lot of valuable feedback that has resulted in many of SCEvents' new functionality and improvements. Cheers Simon.