Yes, it does still apply (the Windows version is not relevant). And SB can evaluate whether that change-event is (or is not) in the scope of any profile (with that option set) by comparing the returned path\name of the change-event to the Source or Dest path and any relative de/selections* of any such profiles till it finds if they are 'involved' or not, or not before deciding to run any profile(s) that is/are ('involved').
But, having made that decision to trigger the profile(s), the point is that SB profiles work from a scan & compare database that drives the rest of the logic, and the full database therefore has to be populated, thus it has to scan anyway. This is how the software works at a very basic level, and is very unlikely to change. Bear in mind that there are potential advantages (for example: if some files changed while SB wasn't open, and we didn't scan anyway next time it triggered OnChange, those earlier 'pending' changes might never get backed up, either in a timely manner or at all)
* de/selections govern whether it triggers/scans at all. Filters, OTOH, are only applied to the results of a scan (they don't determine if it scans or not). Filters can thus prevent unwanted stuff from being copied (e.g. temp files) but they can't prevent the scan taking place if unwanted stuff changes
But, having made that decision to trigger the profile(s), the point is that SB profiles work from a scan & compare database that drives the rest of the logic, and the full database therefore has to be populated, thus it has to scan anyway. This is how the software works at a very basic level, and is very unlikely to change. Bear in mind that there are potential advantages (for example: if some files changed while SB wasn't open, and we didn't scan anyway next time it triggered OnChange, those earlier 'pending' changes might never get backed up, either in a timely manner or at all)
* de/selections govern whether it triggers/scans at all. Filters, OTOH, are only applied to the results of a scan (they don't determine if it scans or not). Filters can thus prevent unwanted stuff from being copied (e.g. temp files) but they can't prevent the scan taking place if unwanted stuff changes