Comment 2 for bug 748840

Revision history for this message
Nathanael Schilling (nathanaelschilling) wrote :

I don't know what all the stati for bugs are, so I don't know what the correct status for this bug would be, though I'm not sure if "Opinion" is the right one, as as far as I can see it is a bug that is also fixable.

With regards to the two user cases above, it is clear that the mechanism for determining where to place a window needs to be somewhat "intelligent", as the current buzzword seems to be, i.e. it would need to take in several factors.

For example, say a user is typing into an application that is open, and does so whilst waiting for another application to open. In this case, I would say that it is obvious that the new window should not open in the foreground. This has been the setting where I have noticed this problem most, and which led me to report it. Basically, the function determing where to place the new window would need to know "what the user is paying attention to", and the only way, as far as I can see to determine this reliably would be if the user were clicking(in the case of a game) or typing much.

As for the first user case, it is clear that this function would also need to take into account whether any other windows are open in the current workspace and to place the window in the foreground if this is not the case.

With the solution outlined above, I think that this bug would be fixed for user cases such as the one where someone is typeing whilst waiting for an application above, without this solution affecting other user cases such as the ones given by Bilal Akhtar negatively.