I noticed your post on the other list you posted this to, and was going
to suggest you try the ActiveX Xtra from the ActiveCompanionSet to see
if it makes a difference: < http://www.xtramania.com/Downloads/VbScriptXtra/>
I've been programming my own activex lately to control USB I/O boards. I'm
finding activeX works a little better in Director MX than MX 2004 where in
the ActiveX won't even load in.
You might want to try making Director jump to a frame that the activeX is
not in when it quits. Also, check that the ActiveX is properly cleaning up
after itself when it terminates. Such as if it has something open, a file, a
"tfiene" <email@example.com> wrote in message
> Hi all,
> Has anyone had problems with the projector not terminating correctly
> when working with the ActiveX Xtra? We are working on a Director
> application that uses some custom ActiveX controls. When the user
> quits the projector, the Process for the projector does not
> terminate. If you look in the Windows Task Manager and click on the
> Processes tab, the process for the projector is still there even
> after the user quits.
> I am using Director MX 2004 on Windows XP Pro. Users with other
> versions of Windows are also seeing the problem.
> One interesting note is that if we put the ActXPriv.x32 user
> interface component in the Xtras folder that the projector uses, the
> problem goes away (the process terminates correctly upon quitting).
> Unfortunately the documentation for the ActiveX Xtra says "Under no
> circumstances should the user interface component 'ActXPriv.X32' be
> redistributed with a packaged Director multimedia title."
> Thanks for any help!
Thanks for the idea Sean. I tried the version of ActiveX Xtra that you mentioned and it does not seem to work.
I'm getting the same problem in D11.5 on windows XPPro SP3 ( some bugs never die )
So when you add the 'ActXPriv.X32' do you still keep the 'ActiveX.x32' in the xtras folder as well?
I just thought that you might fail to unregister your activeX component when you stop the projector (in case you deliver the component's dll to the user with your projector package). Say my component is called axvlc.dll. It is placed in the same directory as my stub projector (given by: _movie.pass)
On startMovie -- I register the component:
axRegSuccess = ActiveXControlRegister(_movie.path&"axvlc.dll")
--axRegSuccess must be -1
on stopMovie -- I unregister it
axUnRegSuccess = ActiveXControlUnRegister(_movie.path&"axvlc.dll")
--axUnRegSuccess must be -1
What if I don't have a component .dll in the same folder as the projector?
I'm using the rtfText box which is a RICHTX32.OCX in windows system32 folder.
Do I still register it like you showed?
I sometimes use windows web browser component (dont know what ocx/dll) I just pick it from the drop list.
If you going to distribute your projector to users without bringing them the activex dll, then you must be sure that the activeX is already installed (means registerd) on the computers of your users, not only on yours. And with your case with the rtf component, it is perhaps automatically so.
Now answerring to your question. No, in your case, you don't have to bring th dll and register/unregister it. At least as far as I understand; I am not an expert in that.