Skip to content
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

Export Wizard launched after modal has wrong button sizehint (buttons too tall) #1913

Open
rocodes opened this issue Mar 14, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@rocodes
Copy link
Contributor

rocodes commented Mar 14, 2024

Description

Known issue from #1777:
If the Export Wizard is launched with the main appwindow as its parent (i.e. user clicks "Export", "Export Transcript", or "Export All" and all files have already been downloaded), the wizard buttons appear at the correct height. However, if the export wizard is launched after a modal ("Some files will not be exported"), the button box takes up too much height, cutting off part of the last line of text in the Preflight message. The buttons remain too tall for the rest of the export flow.

Steps to Reproduce

  • actions -> Export All for a source where some files have not yet been downloaded. Accept the modal confirmation

Expected Behavior

export_transcript

Actual Behavior

button_too_big

Comments

  • The parent widget is affecting the sizeHint of the buttons
  • Part of the problem is that we don't draw the buttonbox and buttonalyout (it's handled by Qt), so we don't have direct access to the layout elements
  • Very brief look: Overriding sizeHint would solve this issue, but that's not possible without extending or reimplementing the button class. Trying to create and use a child class of QWizardButton led to a segfault; that needs more investigation. Trying to implement a QAbstractButton means a lot of implementation. There's probably a better way that involves creating and using a new button layout with setButtonLayout. This needs testing to make sure that we don't lose all the useful features of the existing buttons (advance/return page logic, enabled/disabled state, etc).
  • A quick workaround (looking for the mainwindow and setting it explicitly as the wizard's parent, instead of the modal being the parent) did not work
@rocodes rocodes added the bug Something isn't working label Mar 14, 2024
@rocodes
Copy link
Contributor Author

rocodes commented Mar 14, 2024

I think we should address this at a later date. The possible solutions have more downsides than upsides, especially if we get into creating custom buttons, which would create a larger test/QA burden right before the release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant