This issue was discovered right after 1.6 debuted. And it showed up in the bug tracker (link). It wasn't fixed in 1.6.4, but I remained patient, assuming they would include the fix in the next bigger release. And here we are on 1.7 and it's still an issue??
Dont get me wrong: I am way overly excited and happy with 1.7 and I dont mean to just complain about the first thing I find wrong with it, but how long does it take to fix what seems like a rather simple bug?
Dont get me wrong: I am way overly excited and happy with 1.7 and I dont mean to just complain about the first thing I find wrong with it, but how long does it take to fix what seems like a rather simple bug?