Re: Win32::OLE events callback not executed
I'm willing to pay anyone that can make this work. If anyone is interested, send me a personal email. Thanks On Sun, Mar 25, 2012 at 12:52 AM, haratron harat...@gmail.com wrote: I'm so desperate about this. Could anyone at least point in the right direction? Is WithEvents broken? There's the pyTTS module in Python that succeeds in firing the events. Yet I can't figure out how to port it. On Mon, Mar 19, 2012 at 9:46 PM, Howard Tanner tan...@optonline.net wrote: Thanks anyway Jan. -Original Message- From: perl-win32-users-boun...@listserv.activestate.com [mailto:perl-win32-users-boun...@listserv.activestate.com] On Behalf Of Jan Dubois Sent: Monday, March 19, 2012 3:45 PM To: 'Howard Tanner'; 'haratron' Cc: perl-win32-users@listserv.activestate.com Subject: RE: Win32::OLE events callback not executed On Mon, 19 Mar 2012, Howard Tanner wrote: I couldn't get any events to be fired either. Perhaps Jan can weigh in since he seems to be around today. Sorry, I don't know _why_ it isn't working, but I've seen others run into the same problem with SAPI. Unfortunately I don't have time to play with SAPI stuff myself, so I won't be able to help much. Cheers, -Jan ___ Perl-Win32-Users mailing list Perl-Win32-Users@listserv.ActiveState.com To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs ___ Perl-Win32-Users mailing list Perl-Win32-Users@listserv.ActiveState.com To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
Calling a Perl exe with VB - VB/Windows changing current path
Howdy Fellow Win32 Perl users. At the moment we are in the process of modding a few file munging app's to make them Cross platform - this means taking the existing Perl from our Unix based servers, making them compatible with Win32, compiling using PDK and then modding some existing Windows apps (VB 6) to call the compiled Perl. (We are using the existing VB apps, as apparently Ops can't use command line and don't like change :-( ) Everything seems to work fine until you navigate to a file via the Windows front end, which then changes the current path to where ever the file is located, which the Perl app is picking up on. This is an issue as I want to write a report to a subdirectory of where the app is, not where the files are found. I have overcome the issue at the moment using Cwd 'abs_path' and abs_path($0), then using a substitute to re-construct the path of where the Reports are to go. What I would like to know, is there a way that Perl can keep in control of its current path? Or is this something that I should get our VB guru's to look at? (they have asked me to fix it in the Perl. Maybe they are just being lazy) Cheers Ashley --- Disclaimer: Confidentiality: This message contains privileged and/or confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that you must not disseminate, re-transmit, copy or take any action in reliance on it. If you have received this message in error please delete the document and notify Data Action immediately. Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Data Action. Viruses: Any loss/damage incurred by using this material is not the sender's responsibility. Data Actions' entire liability will be limited to resupplying the material. No warranty is made that this material is free from computer virus or any other defect. ---___ Perl-Win32-Users mailing list Perl-Win32-Users@listserv.ActiveState.com To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
Re: Calling a Perl exe with VB - VB/Windows changing current path
On 13 April 2012 08:37, Ashley Hoff ah...@dataaction.com.au wrote: ** Howdy Fellow Win32 Perl users. At the moment we are in the process of modding a few file munging app’s to make them Cross platform – this means taking the existing Perl from our Unix based servers, making them compatible with Win32, compiling using PDK and then modding some existing Windows apps (VB 6) to call the compiled Perl. (We are using the existing VB apps, as apparently Ops can’t use command line and don’t like change L ) Everything seems to work fine until you navigate to a file via the Windows front end, which then changes the current path to where ever the file is located, which the Perl app is picking up on. This is an issue as I want to write a report to a subdirectory of where the app is, not where the files are found. I have overcome the issue at the moment using Cwd 'abs_path' and abs_path($0), then using a substitute to re-construct the path of where the Reports are to go. What I would like to know, is there a way that Perl can keep in control of its current path? Or is this something that I should get our VB guru’s to look at? (they have asked me to fix it in the Perl….. Maybe they are just being lazy) Haven't checked, but what does http://perldoc.perl.org/FindBin.html report out from the Perl exe in comparison to getcwd? Just in ___ Perl-Win32-Users mailing list Perl-Win32-Users@listserv.ActiveState.com To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
RE: Calling a Perl exe with VB - VB/Windows changing current path
An executable built by PerlApp can call the PerlApp::exe() function to get the location of the executable itself. Cheers, -Jan From: perl-win32-users-boun...@listserv.activestate.com [mailto:perl-win32-users-boun...@listserv.activestate.com] On Behalf Of Ashley Hoff Sent: Thursday, April 12, 2012 5:38 PM To: perl-win32-users@listserv.ActiveState.com Subject: Calling a Perl exe with VB - VB/Windows changing current path Howdy Fellow Win32 Perl users. At the moment we are in the process of modding a few file munging app’s to make them Cross platform – this means taking the existing Perl from our Unix based servers, making them compatible with Win32, compiling using PDK and then modding some existing Windows apps (VB 6) to call the compiled Perl. (We are using the existing VB apps, as apparently Ops can’t use command line and don’t like change L ) Everything seems to work fine until you navigate to a file via the Windows front end, which then changes the current path to where ever the file is located, which the Perl app is picking up on. This is an issue as I want to write a report to a subdirectory of where the app is, not where the files are found. I have overcome the issue at the moment using Cwd 'abs_path' and abs_path($0), then using a substitute to re-construct the path of where the Reports are to go. What I would like to know, is there a way that Perl can keep in control of its current path? Or is this something that I should get our VB guru’s to look at? (they have asked me to fix it in the Perl….. Maybe they are just being lazy) Cheers Ashley --- Disclaimer: Confidentiality: This message contains privileged and/or confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that you must not disseminate, re-transmit, copy or take any action in reliance on it. If you have received this message in error please delete the document and notify Data Action immediately. Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Data Action. Viruses: Any loss/damage incurred by using this material is not the sender's responsibility. Data Actions' entire liability will be limited to resupplying the material. No warranty is made that this material is free from computer virus or any other defect. --- ___ Perl-Win32-Users mailing list Perl-Win32-Users@listserv.ActiveState.com To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
RE: Calling a Perl exe with VB - VB/Windows changing current path
With PDK compiled EXEs you can also PDK-specific PerlApp::exe() function (http://docs.activestate.com/pdk/9.1/PerlApp.html#perlapp_exe) to easily get the path of the PDK application that's currently executing. So something like: my $folder=PerlApp::exe(); $folder=~ s/(.*?)[^\\\/]+$/$1/; print $folder,\n; HTH - T From: perl-win32-users-boun...@listserv.activestate.com [mailto:perl-win32-users-boun...@listserv.activestate.com] On Behalf Of Ashley Hoff Sent: Thursday, April 12, 2012 6:38 PM To: perl-win32-users@listserv.ActiveState.com Subject: Calling a Perl exe with VB - VB/Windows changing current path Howdy Fellow Win32 Perl users. At the moment we are in the process of modding a few file munging app's to make them Cross platform - this means taking the existing Perl from our Unix based servers, making them compatible with Win32, compiling using PDK and then modding some existing Windows apps (VB 6) to call the compiled Perl. (We are using the existing VB apps, as apparently Ops can't use command line and don't like change :( ) Everything seems to work fine until you navigate to a file via the Windows front end, which then changes the current path to where ever the file is located, which the Perl app is picking up on. This is an issue as I want to write a report to a subdirectory of where the app is, not where the files are found. I have overcome the issue at the moment using Cwd 'abs_path' and abs_path($0), then using a substitute to re-construct the path of where the Reports are to go. What I would like to know, is there a way that Perl can keep in control of its current path? Or is this something that I should get our VB guru's to look at? (they have asked me to fix it in the Perl. Maybe they are just being lazy) Cheers Ashley --- Disclaimer: Confidentiality: This message contains privileged and/or confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that you must not disseminate, re-transmit, copy or take any action in reliance on it. If you have received this message in error please delete the document and notify Data Action immediately. Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Data Action. Viruses: Any loss/damage incurred by using this material is not the sender's responsibility. Data Actions' entire liability will be limited to resupplying the material. No warranty is made that this material is free from computer virus or any other defect. --- ___ Perl-Win32-Users mailing list Perl-Win32-Users@listserv.ActiveState.com To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
RE: Calling a Perl exe with VB - VB/Windows changing current path
Looks like we have a winner! FindBin seems to work perfectly for what I require. I think I would also prefer to use this over PerlApp::exe(), as it gives me just that bit more flexibility, especially considering that it will run on the UNIX environment as well. Cheers From: perl-win32-users-boun...@listserv.activestate.com [mailto:perl-win32-users-boun...@listserv.activestate.com] On Behalf Of Justin Allegakoen Sent: Friday, 13 April 2012 10:18 To: perl-win32-users@listserv.activestate.com Subject: Re: Calling a Perl exe with VB - VB/Windows changing current path On 13 April 2012 08:37, Ashley Hoff ah...@dataaction.com.au wrote: Howdy Fellow Win32 Perl users. At the moment we are in the process of modding a few file munging app's to make them Cross platform - this means taking the existing Perl from our Unix based servers, making them compatible with Win32, compiling using PDK and then modding some existing Windows apps (VB 6) to call the compiled Perl. (We are using the existing VB apps, as apparently Ops can't use command line and don't like change :-( ) Everything seems to work fine until you navigate to a file via the Windows front end, which then changes the current path to where ever the file is located, which the Perl app is picking up on. This is an issue as I want to write a report to a subdirectory of where the app is, not where the files are found. I have overcome the issue at the moment using Cwd 'abs_path' and abs_path($0), then using a substitute to re-construct the path of where the Reports are to go. What I would like to know, is there a way that Perl can keep in control of its current path? Or is this something that I should get our VB guru's to look at? (they have asked me to fix it in the Perl. Maybe they are just being lazy) Haven't checked, but what does http://perldoc.perl.org/FindBin.html report out from the Perl exe in comparison to getcwd? Just in --- Disclaimer: Confidentiality: This message contains privileged and/or confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that you must not disseminate, re-transmit, copy or take any action in reliance on it. If you have received this message in error please delete the document and notify Data Action immediately. Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Data Action. Viruses: Any loss/damage incurred by using this material is not the sender's responsibility. Data Actions' entire liability will be limited to resupplying the material. No warranty is made that this material is free from computer virus or any other defect. ---___ Perl-Win32-Users mailing list Perl-Win32-Users@listserv.ActiveState.com To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
