Summary: | Menus and buttons display offset in blender ATI R200, R300 | ||
---|---|---|---|
Product: | Mesa | Reporter: | Terry Barnaby <terry> |
Component: | Drivers/DRI/r200 | Assignee: | Default DRI bug account <dri-devel> |
Status: | NEW --- | QA Contact: | |
Severity: | normal | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: | Picture showing buttons offset in blender. (Ignore black bits). |
Actually there is the same problem on an ATI R300 based system when in DRI2 mode with kernel modeset. In DRI1 mode (kerenl nomodeset) there is no offset but blender is very slow. I have tried this on an Intel 82915G/GV/910GL machine and it has the same problem. So it doesn't look like it is just an R200/R300 issue ... I have updated the XServer from 1.6.1 to 1.6.99 from Fedora 12 development branch and rebuilt drm/xf86-video-ati/mesa to suit. The blender menus are no longer offset with this setup. However, pop-up menus do no appear until you move the mouse over where they would be. Also the menu buttons don't highlight properly. They seem to highlight when the cursor moves off them ... |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Created attachment 28465 [details] Picture showing buttons offset in blender. (Ignore black bits). This is on Fedora 11 with drm/xf86-video-ati/mesa from git on 2009-08-10 with an ATI RV280 [Radeon 9200 PRO]. When using the mouse to select a menu item it looks like the program thinks that the mouse cursor is 20 or so pixels higher than it is. Ie to operate a menu you have to move the mouse 20 pixels or so below the menu. Also the system will draw some menu items 20 or so pixels above where they should be as well. See enclosed picture. There is no problem on an ATI R300 based system.