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

Winforms stack trace dialog buttons are unreliable #2474

Closed
mhsmith opened this issue Apr 2, 2024 · 0 comments · Fixed by #2475
Closed

Winforms stack trace dialog buttons are unreliable #2474

mhsmith opened this issue Apr 2, 2024 · 0 comments · Fixed by #2475
Labels
bug A crash or error in behavior. windows The issue relates to Microsoft Windows support.

Comments

@mhsmith
Copy link
Member

mhsmith commented Apr 2, 2024

Steps to reproduce

Open the dialogs example, and click "Stack Trace". The dialog appears, and then 1 second later, this appears in the console:

Task was destroyed but it is pending!
task: <Task pending name='Task-1' coro=<handler_with_cleanup() done, defined at C:\Users\smith\cygwin\git\beeware\toga\core\src\toga\handlers.py:36> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x000002612A605880>()]>>

Click the OK button. Nothing happens.

Click the close button. The dialog closes.

This only happens the first time you open the dialog in a process. In all subsequent dialogs, the OK button closes the dialog but the close button does not.

Expected behavior

Based on the code, it looks like the intention is that the OK button closes the dialog but the close button does not.

Environment

  • Operating System: Windows 10
  • Python version: 3.8
  • Software versions:
@mhsmith mhsmith added bug A crash or error in behavior. windows The issue relates to Microsoft Windows support. labels Apr 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug A crash or error in behavior. windows The issue relates to Microsoft Windows support.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant