At 02:20 AM 3/7/2012, you wrote: > > So for cross-platform folder notifications, I'd use these classes? > > > > Windows: WindowsFolderChangeMBS > > Mac 10.5+: FSEventsMBS > > Mac 10.4: FolderChangedNotificationMBS > > > > Why use FSEventsMBS? Won't FolderChangedNotificationMBS work just > > fine? I want to continue to support Tiger. > >FSEvents is for all applications and from the system level. >FolderChangedNotificationMBS is from supported applications which >notify others about changes. > >Same for WindowsDirectoryWatcherMBS (System) vs. >WindowsFolderChangeMBS (Explorer).
Oh, okay. So the difference is that if I look at a folder in WindowsFolderChangeMBS, and some app writes a file in that folder, I won't be notified, but if I delete a file in that folder using Windows Explorer (the shell, that is), I will be? But if I use WindowsDirectoryWatcherMBS, any change will be given notification? Similarly, if an app uses the Shell commands/API to write/delete/edit a file, I'd be given notification through WindowsFolderChangeMBS because the app is actually using the Shell (WIndows Explorer) to do it's dirty work instead of (for example) open() or mkdir() or some system level thing? (And of course, the Mac seems to parallel this, the difference between Finder API/commands and low level file handling.) So there is no system-level folder notification in MBS for 10.4? Okay, I think I'll use the system functions, I want to know all folder changes and I don't care who makes them. ----- On a related but different topic, have you ever consider making a set of classes run "on top" of your other classes to wrap them into being cross-platform? It seems there's a lot in MBS that have separate Mac-specific and Win-specific classes for the same thing. The Notification is a good example. It's up to the users, if they wish, to come up with their own cross-platform wrapper for both classes. While that's fairly simple to do, if you did it it seems that it would tie together your library to make it a bit more simpler, and bit more concise. Even if you limited the access/capabilities out of necessity, and that wasn't enough for someone, anyone could just make their own wrapper out of the divided classes like they do now. You could put this into MBS itself, or perhaps you could make it a separate product? Besides, REAL's #1 selling point is cross-platform, so what do you think? Garth Hjelte Sampler User _______________________________________________ Mbsplugins_monkeybreadsoftware.info mailing list [email protected] https://ml01.ispgateway.de/mailman/listinfo/mbsplugins_monkeybreadsoftware.info
