Okay, I'll assume you don't really mean 'in gcc', but 'using the C language'. Within the scope of the C language as commonly used in Linux (this is LinuxQuestions.org), there is no such functionality. You can trap system signals with the linux 'signal()' system call, but that won't accomplish any 'file-copy and paste' event trapping. File IO is the purview of the linux kernel and, as such, is probably not detectable as an 'event'.
Two schemes that come to mind for accomplishing your objective are:
1.) Periodic polling of the file(s) in question. This begs the questions of how often to poll, and what, exactly, to poll. How often is fast enough? How many files do you have to test? Unless the application uses a finite predefined number of files, this is probably not a solution. This is the scenario of many applications such as file editors that detect when another program has modified a file that is currently open and in use by the application.
2.) Use of a virtual file system. Using this method, your application presents itself to the system as a mountable filesystem. Access to your application's functionality is through standard file IO system calls (ie. open-read-write-close) calls. Your application provides a predefined set of callbacks that respond to these system calls and thereby provide the desired functionality. There is a nice library to help with this kind of thing; 'Fuse, Filesystem in UserSpace' at
http://fuse.sourceforge.net I have successfully used this package in my work. There may be other packages which provide similar functionality.
Now, it also sounds like you may be referring to GUI oriented actions, like 'drag and drop' types of events. These would fall in the domain of the 'desktop' GUI, as I understand it. To trap these sorts of actions, you will need the development libraries and documentation for your target GUI environment. I guess these would be things like GTK and Qt development packages. May I humbly suggest that these are probably not the level at which to base an interface to anything I would describe as a 'driver'.
Hope this helps.
--- rod.
