The current system already acts quite intelligent:
It will choose the workspace to maximize on that holds the biggest part of the window...
But this system could be improved, my idea:
We could upgrade the logic to not only take the window's position, but also the mousepointer's position into account.
We would have to be very careful though when to also check the mousepointer's position to not introduce unwanted regressions here: On multimonitor-systems the mousepointer could be on the other screen, while the user maximizes a focussed window per keyboard shortcut for example.
But including the mousepointer' position in the maximize viewport calculation could bring a solution here...
Also a quick peak on the HUD's positioning code could also help as the HUD will never open off-screen.
The current system already acts quite intelligent:
It will choose the workspace to maximize on that holds the biggest part of the window...
But this system could be improved, my idea:
We could upgrade the logic to not only take the window's position, but also the mousepointer's position into account.
We would have to be very careful though when to also check the mousepointer's position to not introduce unwanted regressions here: On multimonitor- systems the mousepointer could be on the other screen, while the user maximizes a focussed window per keyboard shortcut for example.
But including the mousepointer' position in the maximize viewport calculation could bring a solution here...
Also a quick peak on the HUD's positioning code could also help as the HUD will never open off-screen.