Using a simple measure like this, I can see when the RecycleManager is changing its value. Its all fine if you delete files/folders or if you move files/folders directly into the RecycleBin, but it neither does if you move/delete files manually out of the RecycleBin nor if you restore files from your RecycleBin.
Using OnUpdateAction you can doublecheck the current value if you want.
This is a known issue with the Windows API that examines the contents of the Recycle Bin. In the context of an app like Rainmeter, if we have it watching the bin for the actions you described, it becomes a hideous CPU hog. There is no solution in sight at this time.
jsmorley wrote:This is a known issue with the Windows API that examines the contents of the Recycle Bin. In the context of an app like Rainmeter, if we have it watching the bin for the actions you described, it becomes a hideous CPU hog. There is no solution in sight at this time.
Ok, maybe a note in the manual would be a good alternative.