Ticket #3857 (closed: worksforme)
Update Mac Qt to 4.7.4 to avoid QComboBox bug
| Reported by: | Martyn Gigg | Owned by: | Michael Reuter |
|---|---|---|---|
| Priority: | minor | Milestone: | Release 2.6 |
| Component: | Framework | Keywords: | |
| Cc: | taylorrj@…, campbellsi@… | Blocked By: | |
| Blocking: | Tester: | Martyn Gigg |
Description
Jon Taylor showed me a strange bug where if you select an item in any combo box and then leave the box the selection is cleared and the text in the box is blank. After that the boxes cannot be used again as the selection is now always considered invalid.
It turns out that this is a reolved bug in the Qt framework for the Mac, but only when using the CleanLooks style for some reason.
The workaround is not to use the cleanlooks style so this is not as vital to fix but the bug report says it is resolved in 4.7.4 so it may be worth upgrading so that this does not remain an issue
Change History
comment:2 Changed 9 years ago by Nick Draper
- Priority changed from major to minor
- Owner set to Anyone
- Status changed from new to assigned
Discuss solution with mantid-developers before implementing
comment:3 Changed 9 years ago by Russell Taylor
Note that for the Mac we don't use the Third_Party Qt (because it wasn't there at the time things were set up rather than a concious choice), so changing the version is simply a case of installing a different Qt on the build machine and checking everything still works.
We could also decide to rationalise things to use Third_Party for this as well, in which case there would need to be a change for Windows as well since 4.7.2 is the problem version (though presumably 4.7.4 is only a bugfix update).
comment:4 Changed 9 years ago by Martyn Gigg
4.7.4 is only a minor bugfix release. I think the only reason why we have a slightly different one here is because when we got our Mac 4.7.2 was the one available. I guess having a Third_Party one would be better in the long run so that we know everyone is using the same one. I don't know how much work that is though, if CMake is told where the libraries are will it sort everything out in the bundle?
comment:5 Changed 9 years ago by Nick Draper
- Milestone changed from Iteration 32 to Iteration 33
Moved to iteration 33 at iteration 32 code freeze
comment:6 Changed 8 years ago by Nick Draper
- Milestone changed from Release 2.1 to Release 2.2
Moved at end of release 2.1
comment:8 Changed 8 years ago by Nick Draper
- Milestone changed from Release 2.3 to Release 2.4
Moved to milestone 2.4
comment:9 Changed 8 years ago by Nick Draper
- Milestone changed from Release 2.4 to Release 2.5
Moved at the code freeze for release 2.4
comment:10 Changed 7 years ago by Nick Draper
- Milestone changed from Release 2.5 to Release 2.6
comment:11 Changed 7 years ago by Michael Reuter
- Owner changed from Anyone to Michael Reuter
- Status changed from assigned to accepted
comment:12 Changed 7 years ago by Michael Reuter
- Status changed from accepted to verify
- Resolution set to worksforme
Since all platforms are not at version 4.8.x, I don't think this applies anymore. Tested this out with current kit and don't see it. Can anyone confirm?
comment:13 Changed 7 years ago by Michael Reuter
That's now at version 4.8.x.
comment:14 Changed 7 years ago by Martyn Gigg
- Status changed from verify to verifying
- Tester set to Martyn Gigg
comment:15 Changed 7 years ago by Martyn Gigg
- Status changed from verifying to closed
Works here too.
comment:17 Changed 5 years ago by Stuart Campbell
This ticket has been transferred to github issue 4704
Over here we (well me and the buildserver at least) are using Qt 4.7.0 and haven't seen this issue (though I haven't seen it on an installed version either, come to that...)