First of all, how's the Portuguese - Brazilian translation?
I can do this as well, if needed...
I have been thinking about the "no keep tracking of files moved by windows explorer" problem...
Actually, I had an unfinished similar project like yours, and that problem isn't just on windows explorer, but on every software that perfoms files operations.
So, one of my ideas was intercepting any file operation directly, and thus, integrate all theses operations with "Tabbles" needs.
This can be done by DLL injection on Windows' APIs, like Microsoft Detours does.
Detours costs $ 10,000, but, based on some studies, I think it's not that dificult to make something similar.
You just need to develop an installation that finds the files operations functions in Windows APIs and rewrite their calls to redirect them to your own dll.
But this injected dll will just store the information to test later because at this time you don't know if the file operation will be successful.
After this storage, you redirect the flow back to the original function, to have the file operation performed properly.
Or, once in your function, maybe you could make it call the original function before, and then integrate the operation directly to "Tabbles", without the "log-storage and post-testing".
It requires some low-level skills, but I couldn't find any most effective and guaranteed way of keep tracking of all the files at real time...
What do you think?
Sorry any bad english...
)
