Register
(2015-04-10, 14:27)rickwookie Wrote: Any chance of getting this issue that was previously fixed by build #0316 and broken again by build #0322 re-fixed?!