
I wasn't able to recreate this problem reported long back on fsf-ap mailing-list. However setting the Nglayout.initialpaint.delay value too high seems to give similar results. Can anyone show some insight into this problem.
I wasn't able to recreate this problem reported long back on fsf-ap mailing-list. However setting the Nglayout.initialpaint.delay value too high seems to give similar results. Can anyone show some insight into this problem.
No comments:
Post a Comment
You can leave a comment here using your Google account, OpenID or as an anonymous user.