Tone thing to try would be to switch the debugger to "local" debugging and see if that makes
 a difference.  Run

 

                pdkdebug -local

 

To switch to local debugging and maybe also make sure you delete the PERLDB_OPTS and PERL5DB
 environment variables from your shell.

 

The difference between local and remote debugging would be that local debugging starts the d
ebugger GUI directly from your Perl
process whereas in remote debugging the GUI is launched by the pdkdebug service, and the lat
ter obviously would have no idea where
the actual Perl program is running, it could be on a different virtual desktop, or even on a
 different machine.

 

Even in local debugging mode the GUI will be launched via OLE Automation.  I would hope it w
ould launch on the same desktop as the
perl application itself, but if it doesn't, then there is not much we could do about this in
 the PDK; it would be an issue of either
COM/OLE or the virtual desktop software to get this correct (it is the same as spawning Exce
l from perl via Win32::OLE and Excel
then appearing on a different desktop).

 

Cheers,

-Jan

 

From: pdk-bounces@[...].com [mailto:pdk-bounces@[...].com] On Behalf Of Allan Clarke
Sent: Friday, July 31, 2009 7:51 AM
To: pdk@[...].com
Subject: graphical debugger not interacting well with virtual desktops

 

Greetings, Jan!

 

I use the free virtual desktop manager from Sysinternals (http://technet.microsoft.com/en-us
/sysinternals/cc817881.aspx). I like it
because it is a real VDM and does not try to fake desktops by hiding groups of windows. When
 I start the Perl debugger in the PDK,
it always comes up in the first desktop, even if I'm in some other desktop. Its quick to dow
nload and run the VDM (called
desktops.exe) since there is no installer.

 

 

 

Allan Clarke

Software Architect/Lead Developer

HyPerformix, Inc.

5001 Plaza on the Lake, Suite 102, Austin, TX 78746

Office: 512.425.5149

www.hyperformix.com

 

HyperformixLogo_Color_email