> I originally thought this was tied in to the vList xtra I'm
> using, but I just got it from doing 'put basysfolder("prefs")'
> in the message window...
>
> A weird alert that says 'is3dCastMember unknown error
> code(-2147219478)' --
> and I'm not even using any 3d cast members....
Well, I just pulled a fresh copy of BuddyAPI, dropped it into my Director MX
folder on Windows XP Pro, launched the app and tried calling
baSysFolder("prefs") just as you were. I didn't recieve any error like the
above. Hmmm...
Are you on Windows or Mac when you recieve this error?
Are you using a registered version of BuddyAPI or not?
Does this same error happen for you if you open a new movie and enter the
code in the Message Window?
I can confirm that is3dCastMember is an internal Director call but I haven't
the foggiest idea why BuddyAPI's baSysFolder() call would trigger it, and it
doesn't appear to be happening on my end in my ultra-quick test. If we can
reproduce this in some way I'd like to get it logged as a bug so please let
me know if my test is off the mark from your own.
[I'm replying separately to each list as I don't much like cross-posting,
sorry]
Cheers,
Tom Higgins
Product Specialist - Director Team
Macromedia
DIRECTOR, de lekkerste!
...
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/lingo-l.cgi To post messages to the list, email [EMAIL
PROTECTED] (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping
with programming Lingo. Thanks!]
