Macromedia Director Xtra's Issue.

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Macromedia Director Xtra's Issue.

Jump to solution
1,409 Views
viji
Contributor I
Hello Group,


Since I am new bee to the lingo scripts, I am looking forward help form experts of Director Xtras developer.

We have a startup Director movie, which is developed in Director Version 7. Now I am trying to open the same Director movie on Director MX 2004 Version 10.1 Trial version( On Mac OS X Version 10.4.6 ).

I am facing some strange problem in the Lingo script. The startup Director movie ( developed in Director Version 7 ) depends on some Xtras, we have the source code for those Xtras. I could be able to build those Xtras under CodeWarrior IDE 4.1. The result of the build product is Macromedia Director/Shockwave Xtra ( obtained after changing the Creator and Type settings under the code warrior project setting ). I installed the built Xtra in Xtras folder
of the Director application ( Mac OS X 10.4 platform ). I tried to use the installed Xtra by using initialising the Xtra like,

Obj = xtra( " TestXtra " ) . new()
put xtra( " TestXtra " ) . interface()


but the Director is giving script error like TestXtra not found. What would be the workaround for this problem...?

Is there any documentation on how to use such Xtras...

Is there anything additional settings that we need to do with the Director or with the Codewarrior to build Xtra...!


But I downloaded a Xtra named QTAudioXtra from the Internet. The project file of the QTAudioXtra is in CodeWarrior IDE 5.1. I compiled the source under CodeWarrior IDE 5.1 and used the built Xtra as like third party Xtras. This worked fine. In this project while compiling I used Carbon library. But in the project which I mentioned in the beginning I did not used any Carbon library.

Is this cause problem...

Any inputs for this issue...

Looking forward for your reply...

Thanks in advance,
Viji

Message Edited by viji on 2007-06-18 02:21 PM

Message Edited by viji on 2007-06-18 02:22 PM
Labels (1)
Tags (1)
0 Kudos
1 Solution
620 Views
J2MEJediMaster
Specialist I
This is not a Macromedia Lingo problem, it is access to a plug-in issue. In order for Director to access the plug-in it uses the Carbon Library to set up the ABI to both the plug-in  and OS X properly. So, you need to add CarbonLib to the project. However, be aware that CodeWarrior hasn't supported Mac OS X platform development for several years. You may want to look for a plug-in code example for Director that uses Apple's XCode development tools.

Sorry I can't be of more help than that.

---Tom



View solution in original post

0 Kudos
1 Reply
621 Views
J2MEJediMaster
Specialist I
This is not a Macromedia Lingo problem, it is access to a plug-in issue. In order for Director to access the plug-in it uses the Carbon Library to set up the ABI to both the plug-in  and OS X properly. So, you need to add CarbonLib to the project. However, be aware that CodeWarrior hasn't supported Mac OS X platform development for several years. You may want to look for a plug-in code example for Director that uses Apple's XCode development tools.

Sorry I can't be of more help than that.

---Tom



0 Kudos