Bug 1187796
| Summary: | grass has UI issues with wxPython 3.0 | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Scott Talbert <swt> | ||||||
| Component: | grass | Assignee: | Devrim Gündüz <devrim> | ||||||
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | rawhide | CC: | cristian.balint, devrim, neteler, pertusus, volker27 | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2015-02-13 00:15:13 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
Created attachment 986272 [details]
another screenshot
The new version GRASS GIS 7 is addressing this issue of wxPython 3 compatibility: http://trac.osgeo.org/grass/wiki/Release/7.0.0RC-News http://trac.osgeo.org/grass/wiki/Release/7.0.0RC-News#GUIchanges --> updated to better support wxPython3 Anyone want to do a scratch build of the RC? :-) It turns out these issues were due to a GTK+ bug which has been resolved in Rawhide. Closing as NOTABUG. |
Created attachment 986271 [details] screenshot For Fedora 22, Rawhide has been updated to include wxPython 3.0. When running grass with this updated wxPython, there are some UI issues: overlapping text on main screen, menu icons are not sized correctly, etc. See the attached screenshots. From looking at the upstream changelog, it appears upstream is working on resolving wxPython 3 issues. Not sure if these specific issues have been resolved, so it might be good to see how a current trunk build performs.