I did get Crtl-C to work. But it took some experimenting. So I am not sure that I know all the steps that I did to get it working. I gave someone else the settings that I had and they say it still does not work. The setting that finally allowed me to use Crtl-C was to go into Setup, Keyboard and define my break key as Crtl-A.
When I am in Unidata and press Crtl-A, I end up at UNIX. But Crtl-C does now get me into the Unidata debugger. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Andy Pflueger Sent: Wednesday, June 13, 2007 7:26 AM To: U2 User Group Mailing List Subject: [U2] wIntegrate V6 break key woes Hello, Recently, I have installed wIntegrate Version 6.0.4 on my WinXP Pro machine for evaluation use. So far, I really like its enhanced features but have noticed one difference between the previous version which I had loaded. My defined break key is reacting differently. Always before I could use Ctrl-Pause/Break to break a program to the debugger. Now, with the new 6.0.4 version, neither Ctrl-C or Ctrl-Pause/Break will break a program to invoke the debugger. Moreover, the Ctrl-Pause/Break will abort the connection with the server altogether. Has anybody seen or encountered this issue before and how can I change the behavior of the Ctrl-Pause/Break to NOT close the host connection but instead just break the program for the debugger? Thanks in advance, Andy Pflueger Ivy Hill Corporation Louisville, KY Unidata 7.1.0 Solaris 8/9 wIntegrate 6.0.4 ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
