Apps become unresponsive (appear frozen) when a dialog is up

[jcward]

It's understandable that an app would not be interactive while a dialog is up, but the apps I've tested (hxScout, snow basic testcase) become, while the dialog is open, unresponsive is such a way that it produces undesirable results.

On linux, the window becomes gray and dark (like when a runaway process is no longer responding to the OS.) On windows, it's worse such that the app window gets painted over by the dialog.

It's not an absolute blocker, because the app does come back once the dialog is closed. But it does look bad.

snow basic test on linux (note dark app behind dialog):

hxScout on linux:

hxScout on windows (especially bad, the dialog graphics are drawn over the hxScout window):

[ruby0x1]

I'll test this on non vm, I've never encountered this specifically on all three targets with the ones in snow (as mentioned). Will look into it√

[jcward]

FYI, hxScout on Mac showed no visible sign of trouble, though the FPS meter jumped when the file dialog closed, so I think it was exhibiting similar behavior. But still, it's the best UX of the platforms.

And FWIW, the nativefiledialog library exhibited the same behavior.

Makes me wonder about silly workarounds like launching the dialog as a standalone app where the title / filters / result are passed via STDIN / STDOUT. :)

[jcward]

You're right, on a Windows (non-VM), I don't see the overpainting issue -- the app window just sits there (non-interactive) as expected. So VM aside, it seems like perhaps Linux is the only trouble, but it's not a terrible UX.