> Code attached.
Oh god what a breath of fresh air! Windows has a way of making one myopic.
Of course, diving right back in, it's interesting that that code will work
almost exactly as-is when compiled for Win32. The only things I saw right
off hand that need changing are fork() (use CreateProcess) and perror() (use
printf to stderr). Of course the includes need to be changed but that's
trivial.
-SHAWN-
---
You are currently subscribed to vrf as: rsb@soco.agilent.com
To subscribe send a blank email to "join-vrf@it.lists.it.agilent.com".
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Send your favorite VEE example to "VRF-EXAMPLES@agilent.com" for possible inclusion in VEE 7.0!
Oh god what a breath of fresh air! Windows has a way of making one myopic.
Of course, diving right back in, it's interesting that that code will work
almost exactly as-is when compiled for Win32. The only things I saw right
off hand that need changing are fork() (use CreateProcess) and perror() (use
printf to stderr). Of course the includes need to be changed but that's
trivial.
-SHAWN-
---
You are currently subscribed to vrf as: rsb@soco.agilent.com
To subscribe send a blank email to "join-vrf@it.lists.it.agilent.com".
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Send your favorite VEE example to "VRF-EXAMPLES@agilent.com" for possible inclusion in VEE 7.0!
As long as you don't allow Object Refs to linger on data inputs/outputs,
there should be no need to turn off the debug features. Just use variables
for Object References, and delete them when necessary.
If you use a formula box with: "set var1=createobject("jlh.ljh")", be
careful that the default data output "Result" does not hold the reference.
Delete the data output.
Andrew Fudge
Genesys IBS
Wales, UK
----- Original Message -----
From: "Richard Kleinhenz" <scubaman@us.ibm.com>
To: "VRF" <vrf@agilent.com>
Sent: Tuesday, February 03, 2004 2:00 PM
Subject: [vrf] RE:quitting Excel... once more for the Gipper!
>
>
>
>
> That indeed works, thanks! Unfortunately, I really like the debug
features
> in the development environment. Sort of defeats the purpose to turn them
> off... I know, I want to have my cake and want to eat it too!
of
> course there is no way to turn off the debug features programmatically...
> or is there?
> --
> Regards,
> Rich
> ===================
> Richard Kleinhenz
> Wafer Engineering
> 845-892-2617
> scubaman@us.ibm.com
> ===================
>
>
>
> "LOPEZ,PACO
> (HP-Spain,ex2)"
> <paco.lopez@hp.co To
> m> Richard
> Kleinhenz/Fishkill/IBM@IBMUS
> 02/03/2004 04:40 cc
> AM
> Subject
> RE: [vrf] RE: Problem with Excel
>
>
>
>
>
>
>
>
>
>
> Hi Rich,
>
> Try checking the 'Disable debug features' checkbox in the default
> preferences. This really closes the excel process after an .quit() event.
>
> Best regards,
>
> Paco
>
> -----Original Message-----
> From: Richard Kleinhenz [mailto:scubaman@us.ibm.com]
> Sent: Monday, February 02, 2004 6:20 PM
> To: VRF
> Subject: [vrf] RE: Problem with Excel
>
>
>
>
>
>
> Well, maybe I am missing something, but I am a vxl user and during
> development I do have to use the kill process. If I am in the development
> environment, run a test program that does something to an excel file
(after
> the program stops), and want to check that file, it will not open. I have
> to kill the running excel process manually before I can open ANY excel
> file. If there is a workaround of some sort, I'd love to hear about it.
> It gets old pretty fast during development. Of course I suppose I could
> set a breakpoint before the file is saved.... Now why didn't I think of
> that?
> can't look at another excel file either.
> --
> Regards,
> Rich
> ===================
> Richard Kleinhenz
> Wafer Engineering
> 845-892-2617
> scubaman@us.ibm.com
> ===================
>
>
>
> "Greg Wale"
> <gregwale@passtec
> hnologies.com> To
> VRF <vrf@agilent.com>
> 02/02/2004 11:19 cc
> AM
> Subject
> [vrf] RE: Problem with Excel
> Please respond to
> "Greg Wale"
>
>
>
>
>
>
>
>
> Hello Marco,
>
> There are a lot of reasons why Excel doesnb
---
You are currently subscribed to vrf as: rsb@soco.agilent.com
To subscribe send a blank email to "join-vrf@it.lists.it.agilent.com".
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Send your favorite VEE example to "VRF-EXAMPLES@agilent.com" for possible inclusion in VEE 7.0!