Glen was suggesting back then to use #0#0 instead of '' to clear the URL
(try clearing btw. the URL first, then assign a new URL)
---------
The URL property already is a WideString. String would not work, as the
QTControl library is expecting a BSTR. Although I found it hard to believe
at first, it seems that Delph actually is passing a Nil when an empty string
is specified. I walked through the CPU window, and that was what was
happening. By constructing a widestring with #0#0 in it, that will be passed
on to the Library, which will see it as an empty string.
I'm currently using Delphi 2005, I have not upgraded to service pack 3 yet,
as the disks are not at my office
---------
Btw, else try my QTVRControlX control (http://qt4all.onestop.net)
----------------
George Birbilis (email@hidden)
Computer & Informatics Engineer
Microsoft MVP J# for 2004-2007
Borland "Spirit of Delphi"
3D, QuickTime, QTVR, Java, Delphi,
ActiveX, .NET components, Robotics
http://www.kagi.com/birbilishttp://birbilis.spaces.live.com
> -----Original Message-----
> From: quicktime-api-bounces+birbilis=email@hidden
> [mailto:quicktime-api-bounces+birbilis=email@hidden] On
> Behalf Of Warrick Wilson
> Sent: Friday, March 23, 2007 4:12 PM
> To: email@hidden
> Subject: QTControl ActiveX Component
>
> Google was my friend, as I found a thread off messages with this
> subject
> from back in August 2006. Glenn Anderson was describing what sounds
> like my
> problem using the QTControl - after some number of files assigned to
> the
> control, "bad things" happen - instability, crashes, access violation
> messages, etc. I'm also using Delphi (Delphi 7 currently).
>
> I tried the suggested remedy of making sure that I don't assign '' as
> an
> empty string to the URL property. I put that in, but after a "while"
> (and
> that's variable between machines), I get an access violation message
> referring to Quicktime.qts. I'm going to try and dig through that today
> and
> see if I can figure out what's actually being addressed - the message
> does
> give a location within the file.
>
> Is the QTControl stable enough for long-term use in a program? I've
> reverted
> to using the plugin approach that I used with Quicktime 6. The quality
> is
> worse - lots of tearing in video playback - but it runs. I use the
> SkyLight
> library to access the Quicktime plugin - that works well.
>
> However, people have seen the quality difference and would prefer to
> use the
> newer version. But I need it to last more than a "short time". Some
> machines
> play video "loops" for hours at trade shows, etc., and I need it to
> stay
> running without access violation dialogs.
>
> Thanks.
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> QuickTime-API mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
> http://lists.apple.com/mailman/options/quicktime-
> api/email@hidden
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
QuickTime-API mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quicktime-api/email@hidden
This email sent to email@hidden
