If a Perspectives user is working on a laptop and has multiple monitors enabled, then puts the laptop into suspend or sleep mode, then disconnects from the secondary monitor (e.g. undocks), then resumes operation, it's possible for TM1 to try to display windows and dialogs on the monitor which is no longer connected. If the new window/dialog is non-modal, it appears that the system has not responded to the user command. If the dialog is modal, it's possible for the application to appear to freeze.

A workaround is to use the Windows Key + left/right arrow. However, Perspectives should poll workspace configuration and if a window/dialog is mapped to a non-viewable region it should remap it to a visible region to avoid this situation.

(As an aside, it's crazy that I have to submit this as an RFE and not a PMR-- this is textbook "defect" to me.)

This happens to me every day pretty much; I will be voting for it later when I get a chance to scan what else is on there for my quarterly "laugh at all the things which should have been implemented 20 years ago" session.

I did vote for this one, but I won't hold my breath. IBM have their hands full with things other than fixing a century-old defect in a client that has been put on death row. And they always have the free get out of jail card in the form of 'nowhere does it say that we officially support multiple screens'.