> Am I wrong ?
No, you're right, and honestly this is a known (and unfortunately
not well documented) issue that the 3.6 developers didn't have the time to
fix before the release -- there are others too. You know these are the
typical issues marked with a "// FIXME" in the code, but which have a
rather low priority.
In principle that should make it in a 3.6.x some time :-)
- NC
Post a reply to this message
|