Apr 122012

Oops! I’ve just noticed a wee bug in v2.0.0 of jqDock, regarding the new noAntiFlutter option.

jqDock has had some anti-flutter code in it for a while, and I was asked to provide a means for disabling that code … which is why the noAntiFlutter option was introduced in v2.0.0. The intention was to keep the default options all working as before, ie. leaving noAntiFlutter turned Off (the default) would still run the anti-flutter code; and only by specifically turning noAntiFlutter On would the anti-flutter code be by-passed.

Unfortunately, I have somehow got the option back-to-front. Sorry! This means that in order to run jqDock v2.0.0 with the same anti-flutter code as previous versions had by default, you actually need to turn noAntiFlutter On!

The simplest way to do this is to modify the jqdock defaults immediately after the script has been loaded, which avoids having to change any individual Dock options you may have set up, eg:

My sincere apologies for any inconvenience this may cause, and I’ll fix it in the next version asap.


If you want to do it in a way that doesn’t require the inserted code to be removed if/when you upgrade to the next jqDock release, you can expand on the code above by testing for the version…