That is a different issue, then. I'll check it in the latest developer build, and create a bug report, if required (I checked earlier, but didn't see one).