🚀 go-pugleaf

HI,

> > One time hit run doesn't function... but about 100-200 x run
> > functions..:-)) (Pressing and holding F9 several seconds)
> > It seems, the Windows XP NTDLL.dll has several internal breakpoints
> > and quicktime weaks them up in initialising... so the debugger goes to
> > it,...without any influence from borland or QT...
>
> Sounds like there is still something wrong with your setup. This has never
> happened to us using winnt or win2k


It's simple the call "QTInitialize()" which causes the NTDLL.dll -
breakpoints... but that's now not so exciting, because the build runs
without interruption...
but also the "ExitMovies()" deinitialising causes an Error (Access Error)
which also occours with the final build (The quicktime.qts causes an error
in ntdll.dll and kernel32.dll)


> > BTW: If anybody knows, how to stay with full Movie-Size but look at
> > the Movie in the COntroller-specified Rect, so you can export the
> > movie (after copy and paste) without loss of quality, I would very
> > happy, he could told me...also, if anybody knows, how to implement a
> > custom progressbar, that shows the movie playing...
> >
> >
> Apple host some quite good mailing lists for quicktime that it is probably
> worth you subscribing to. That is where I ended up getting most of my
> information from.

I've sucribed the quicktime-api list... or is there any other better for
programming issue?
(In the list there is for several days nobody so nice like you and try to
answer a few questions...;-( )

If you have any hint to me, how it's the best strategy with refreshing
Form-Elements and Movies to avoid flicker, it would be great...
In the most movies, the actual movie frame will first shown, if i move the
whole form, a form-refresh and movieUpdate and movieTask don't help...?

Best regards,
Bjoern