I tried Fences a longish time ago. I removed it very shortly after installation because my machine slowed down noticeably (XP). I also noticed that when I changed things in Fences there was no Save subsequently offered (to a Config file, for example). This can only mean that Fences is always current, always polling the mouse and keyboard to see what is changed. Nothing nasty, but this program type loads and stays in memory - always watching the system - just like an anti-virus or anti-adware program will do, and so they take up memory and resources. Anti-virus progs are important, Fences is just a facility.

I may have this wrong. But the difference in system speeds from not installed to installed and then uninstalled were very noticeable. If I am wrong here, then an explanation for the very noticeable slowdown following installation is required.

Am I right in thinking that Fences behaves in this way, and continually polls the system? If so, perhaps a change of approach. Accept input, then save to a config file, stop the the polling, and all will be well.

Fences is a nice idea and well executed, but it must not install and remain in memory - constantly monitoring the system. Windows has supplied us with enough "Services" continually running in the background taking up resources already, we need no more.