...on Thu, Jan 10, 2008 at 10:28:34PM -0800, Thor (Hammer of God) wrote: > it turns out, Outlook is doing nothing close to what I feared. > Basically, the second instance sees that another Outlook window is > running in the same interactive logon space, and when it starts, it just > calls another popup in the previous Outlook space and then terminates > itself (that's close enough, anyway). The good news is that there is no > "user hopping" or "boundary crossing" here. Sounds comparable to what the Windows Explorer does when it is not expicitly set to run as a separate process (or started with the /separate switch). Is there some design principle behind this kind of behaviour? Alex.
