Hi,
Wx-ActiveX 0.10 is released
http://search.cpan.org/~mdootson/Wx-ActiveX-0.10/
and
http://www.wxperl.co.uk/Wx-ActiveX-0.10.tar.gz
PPMs in usual repositories.
Following Donovan's question re ShockWave, I have added a new constructor
newVersion
which allows you to specify a version of the type library. This is really what
you should do if you are distributing your code.
I have also included a wrapper for the QuickTime ActiveX control and a small
application that will write a Wx::ActiveX wrapper for any given ActiveX control
(see wxactivex_template / Wx::ActiveX::Template ).
Regards
Mark
Mark Dootson wrote:
Hi,
The XS code has been updated. The particular issue with Win32::OLE is
solved using the code / solution you mentioned. Eric Wilhelm had a
working solution so I incorporated that.
Wx::ActiveX::Flash simply loads ProgID 'ShockwaveFlash.ShockwaveFlash',
which would currently load version 9. I think that the thing to do
(though more experienced ActiveX- er's might correct me) if you wish to
handle changes across versions is to load a specific version of the type
library. Then, assuming that the producers of the ActiveX Control
maintain backward compatibility, you would always get the interface you
expected. So, in your case, if the control had been loading
'ShockwaveFlash.ShockwaveFlash.8' then the change to '9' should not have
affected you.
Hmmm.
So, you would need to have created your own 'Flash' ActiveX wrapper that
was typelib version specific to get around this problem.
I feel a version '0.10' release looming that allows you to specify a
typelib version for the ProgId in the constructor.
Regards
Mark
Donovan Allen wrote:
Thanks for working on this. The project I used Wx-ActiveX in is being
re-written in another language now ( sadly I am not using perl very
often since my target OS is now mostly windows and the perl win32
modules just are not a priority in the perl world) , but was curious
if the C++ code got updated or if this is all changes to the perl
modules only.
I had made some cutom changes (stolen directly from a recent
Win32::GUI ActiveX ... which the Wx was originally based on) that
resolved some issues I was having with the Wx version a couple of
years ago...such as Win32::OLE compatibility issues and a couple other
things ... and the issue was mentioned on this list at some point what
the suggested solution was.
Also curious if the Wx::ActiveX::Flash is able to use the most recent
version of flash. I know this was an issue from Flash version 8 to
version 9 (I think anyway...need to check notes) and after client
upgraded flash (because it prompts you to) their kiosks stopped
working. Instead of resolving it properly at the time, I just had
them migrate back to the previous version since they didn't have need
for the upgrade.
________________________________________
From: Mark Dootson [EMAIL PROTECTED]
Sent: Thursday, April 10, 2008 1:45 PM
To: [email protected]
Subject: Wx::ActiveX - Acrobat etc.
Hi
Wx-ActiveX 0.09 is released
http://search.cpan.org/~mdootson/Wx-ActiveX-0.09/
and
http://www.wxperl.co.uk/Wx-ActiveX-0.09.tar.gz
Wx:ActiveX::Acrobat now works and the interface is documented in pod.
This is perhaps the most useful part of the library working again :-).
It was just a case of reading the manual.
Examples for Acrobat, Flash, Media Player, MS Script Control, IE
Explorer and Mozilla Browser are in the Wx::Demo module that is
installed.
Barring bugs, that is hopefully it for a while. I can't think of
anything else that could be usefully added. Having working Acrobat
and IE modules covers 99% of use I would have thought.
Regards
Mark
