Member
2010-04-20, 06:14 AM
Yeah, it broke in 5.2.2 and apparently I was the only one to report it, so it wasn't deemed necessary to hold 5.2.2 to fix it. Additional people reporting the problem via Help->Send Feedback should help make sure it gets fixed soon.