As the title says: It's currently without any effect. :(
Noted approx 1 hour later, fixed build coming ASAP. Will silent update it.
Fixed. It was a minor typo. I had removed some code that wasn't as deprecated as I thought. Anyway, new upload in about 30 minutes (less probably) will fix the issue. So, at least for those late upgraders the issue will not exist. Either way, a new version will replace even this one before long I'm sure.
Specific fix applies to version of v4.09.22 that was built on 02/09/2011 instead of 02/08/2011.