Intuitively, I don't think that disabling animation would make it run any faster. It will take exactly the same amount of time, but you won't get any visual feedback as to what's going on.

I'm almost forced to reply to this because of the comment implying this problem really applies to 'low end' systems - seeing that almost made me laugh out loud. No offense intended, but if Stardock has the illusion that this is a system configuration issue, please wake up!!! The lag and terrible performance of Fences when dragging a fence on my workstation is astonishing. As a software developer for more than 25 years, I can safely say that if I was charging my customers for something that worked like that, I would be busting my butt to fix it. While I am sure it doesn't happen to all systems, those that it does happen on need not be 'low-end', which strongly suggests a software issue of some sort.

On my system, the re-organizing of fences is so bad it's practically unusable. I'm not talking about a little lag here, and nor am I talking about 'low end systems'. For a program to lag five seconds or more behind mouse input on a 8-core skulltrail-based system running 64-bit windows 7 with high-end graphics hardware is astonishing. Yet that is exactly what happens.

I should post a video of the lag somewhere, because it's so bad it's almost funny. Any program that can perform that darn BADLY on a stupidly fast high-end system has got to be doing something very wrong. The hardware I am running this on is an Intel demonstration system - one which had previously been publicly shown at IDF - and which is on loan from Intel's performance group. It's not something I threw together myself from bits and pieces, and nor is it a $200 Walmart special.

Fences is the only application that I have that acts even remotely this way on this box. It's so bad that I dread attempting to re-organize my fences - which sadly I occasionally am forced to do because of another irritating bug that causes it to load the fences into the wrong monitor under some circumstances (I suspect because it stores the display number in the config, rather than the logical arrangement. Other multi-monitor compatible software that I use doesn't seem to have this problem).

I don't expect that this message will make any difference because it's become pretty clear to me that Stardock seems to have changed direction, with little interest in its utility products anymore. This has left me wishing there was an alternative (to the extent that I've even seriously considered writing an open-source replacement). Fences is potentially incredibly useful but it appears to me (and it seems I'm not alone in thinking this) that Stardock either just doesn't care about it, or can't/won't allocate the development resources it needs.

Hi,

This has been resolved in the latest version of Fences.  Please update your Fences Pro or uninstall and reinstall the free version of Fences.

Zargon

Thanks for the feedback.