New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compare Pane cannot be resized when R charts are present on any perspective for the view #4267
Comments
SS-RR and Tri Mix replaced by Python versions contributed by Fe at the users forum. The intention is to avoid triggering #4267
Another workaround: disabling R. |
Missing from RC2 build, also include the fix to avoid crashes when myPerspective is not set in existing charts and default layouts without R charts to avoid #4267 for newly create athletes. [publish binaries]
On macOS snapshot (9/9/22), with R disabled, the compare pane cannot be resized and still disappears when clicked on. |
I moved this issue to Parking Lot since it is not new to v3.6, I verified it is already present in v3.5 when there are R charts in the view, even when R is disabled. We have no solution, and I propose not to delay v3.6 release anymore just because of it. |
I agree- it is also most likely a Qt bug |
Regrettably building with Qt 6.6.1 doesn’t seem to fix this issue. |
This happens both in Activities and Trends views and across platforms: compare pane disappear when the user try to resize it, and it can be recovered using show/hide compare pane, but not resized.
Know workaround is to remove all R charts from all perspectives of the affected view and restart GoldenCheetah or, as contributed below, disable R and restart.
PS: if an R chart is created/imported/downloaded when the compare pane previously worked normally, the compare pane can be resized. Only after GC restart the compare pane can no longer be resized.
PPS: interestingly this also happens with R charts using the native charts API instead of the R graphics device, likely because the later is created and added anyway.
The text was updated successfully, but these errors were encountered: