hey folks: i'm afraid this fix did not actually make the cut for 6.1.4 or 6.1.5. it's currently targeted for 6.1.6, but i have to be clear here: unfortunately, we can never guarantee that a given fix will make it into a given release--it's always possible that a more urgent issue will force us to reprioritize the list. i apologize that Louis did not make this clear in his response.
it is, however, fixed in 6.2, which has already shipped. thanks for your patience.
... View more