Undocked window gets into run-away window state

[grofaty]

Pinta dev 1.7.0.159 on Ubuntu 14.04.

1. New image.
2. Click and hold on second tab image and move mouse to toolbar to undock the image.
3. ALT+TAB to switch to some other program.
4. Repeat step 4 and you get into run-away window. In my humble opinion window should never escape main Pinta program. If you repeat step 3 to get back to main Pinta program there is empty canvas, but Images pad has an image displayed - so it looks like something broken because of run-away window. Average Joe could have plently of problems of understanding what happened.

[Adolfo Jayme Barrientos (fitojb)]

FYI: it’s not called “run-away”. http://en.wikipedia.org/wiki/Modal_window

[Cameron White (cameronwhite91)]

I'm not clear whether there's really an issue here? The new window can't be a modal dialog, since that would prevent you from doing anything with the main Pinta window. And pressing Alt+` on Ubuntu switches between the open Pinta windows.

[grofaty (grofaty)]

@Adolfo, thank you for the link, but I am not talking about "Modal window" - from your link: Modal window is a graphical control element subordinate to an application's main window which creates a mode where the main window can't be used. --> So in modal window: main window can't be used.

I am talking about run-away window that is not a modal window. Try this:
1. New image.
2. Paintbrush from toolbar.
3. Click Open icon from toolbar.
4. Press ALT+TAB to switch to other applications and try back to Pinta and you will notice Open dialog NEWER runs-away from main Pinta program.
5. Switch back to Pinta and don't close Open dialog, just move it little bit to the edge.
6. Click on canvas and draw (Open dialog is still opened). Result: You can draw, Open dialog is opened and there is no run-away window.

I am talking about a dialog that does not run-away, but it makes it possible to use main Pinta program and undocked window.

[Cameron White (cameronwhite91)]

Maybe the issue is just that the parent window isn't being correctly set for the undocked tabs?

[Cameron White (cameronwhite91)]

Looking into this a bit more (on Ubuntu, where it's more noticeable), we could set the TransientFor property for PlaceholderWindow.PlaceInFloatingFrame(). The downside is that the window is then "always on top", so you'd have to move or minimize it to uncover the base window.
I think this probably doesn't need to be a release blocker for 1.7, though.

[grofaty (grofaty)]

I agree, this is tiny problem, that can be postponed after 1.7.