quicktime - once more into the breech

In article <dowdy-230A9B.15100107062004.TakeThisOut@news.apple.com>,
Tom Dowdy <dowdy.TakeThisOut@apple.com> wrote:

 > In article <mair_fheal-403B8E.13325907062004.TakeThisOut@corp.supernews.com>,
 > edens morgan mair fheal greykitten tomys des anges
 > <mair_fheal.TakeThisOut@yahoo.com> wrote:
 >
  > > GraphicsExportSetInputGraphicsImporter(ge,movie);
 >
 > A movie isn't a graphics importer. If you have any kind of param
 > checking turned on in your compiler, this should have kicked out tons of
 > errors.

most of these things are void pointers so checking is turned off

 > You probably want to get the Picture from the movie via GetMoviePict and
 > then use GraphicsExportSetInputPicture.

thank you
thank you
thank you
thank you
thank you
thank you
thank you
thank you
thank you

it works
exactly what i need

thank you

  > > also
  > > where are the damn headers that define
  > > GraphicsExportComponent
  > > and all the rest if anybody knows
 >
 > Movies.h ImageCompression.h
 > If using framework style includes, QuickTime/QuickTime.h will haul all
 > of them in.

with cocoa the documentation gives the import directive
everytime with carbon i have to spend a hour or two looking
for the framework and include and all
cause i cant find any documenting map on what is where

offhand ive forgotten again find out what macos error numbers mean
while i can get unix errnos in one or two tries

  > > i wish apple could figure out how to write man pages
 >
 > There's gobs of QuickTime documentation and sample code online. It
 > isn't man pages, but there is quite a bit of it there.

it returns a pict handle
if you look up the documentation on how to write out the pict to a file
you end up with pascal code use fs-specs

it takes a half-dozen calls to go from a c string to cfstring to url
to fsref to ?fsspec to a file desingator
and still it didnt work (error -35)

since osx can use the extension instead of the finder info
i was able to open the file with
int fd = open("temp.pict",O_WRONLY|O_CREAT|O_TRUNC,0644);
and do it in one step

the carbon interfaces and their documentation are real mess<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: quicktime - once more into the breech 

In article <mair_fheal-416658.16384407062004.TakeThisOut@corp.supernews.com>,
edens morgan mair fheal greykitten tomys des anges
<mair_fheal.TakeThisOut@yahoo.com> wrote:

 > since osx can use the extension instead of the finder info
 > i was able to open the file with
 > int fd = open("temp.pict",O_WRONLY|O_CREAT|O_TRUNC,0644);

 > it takes a half-dozen calls to go from a c string to cfstring to url
 > to fsref to ?fsspec to a file desingator
 > and still it didnt work (error -35)

That's only because you don't know what you are doing. For your example,
with the error checking that is missing from your POSIX example:

#include <Movies.h>
#include <TextUtils.h>

Str255 s;
OSStatus e = noErr;
short ref = 0;
FSSpec fs;

CopyCStringToPascal("temp.pict", s);
if(noErr == e){ e = FSMakeFSSpec(0, 0, s, &fs); }
if(noErr == e){ e = OpenMovieFile(&fs, &ref, fsRdPerm); }
..... do the work
if(0 != ref){ e = CloseMovieFile(ref); }


error codes are mostly in MacErrors.h.

Most people set up their editor to search recursively in:

.../Metrowerks CodeWarrior 8.3/Metrowerks CodeWarrior/MacOS
Support/Universal/Interfaces/CIncludes


and if that doesn't work, the newer stuff can be found by the slower
recursive search of:

/System/Library/Frameworks/

David Phillip Oster<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: quicktime - once more into the breech 

In article <oster-4AE361.22025808062004.RemoveThis@news.sf.sbcglobal.net>,
David Phillip Oster <oster.RemoveThis@ieee.org> wrote:

 > In article <mair_fheal-416658.16384407062004.RemoveThis@corp.supernews.com>,
 > edens morgan mair fheal greykitten tomys des anges
 > <mair_fheal.RemoveThis@yahoo.com> wrote:
 >
  > > since osx can use the extension instead of the finder info
  > > i was able to open the file with
  > > int fd = open("temp.pict",O_WRONLY|O_CREAT|O_TRUNC,0644);
 >
  > > it takes a half-dozen calls to go from a c string to cfstring to url
  > > to fsref to ?fsspec to a file desingator
  > > and still it didnt work (error -35)
 >
 > That's only because you don't know what you are doing. For your example,
 > with the error checking that is missing from your POSIX example:

actually its the call to convert an fs-ref to an fs-spec
required the file to already exists
and i couldnt find the equivalent of fspcreate

thats when i punted the whole thing and used the unix calls
because i remember osx can identify off the extension instead of finder info

if youve done as much unix program as i have
you see what a mess the macintosh interface is
you still have interfaces that go all the back to 1984
that should be shuffled off to appendices as strongly deprecated

for example there is no need any longer for things like fsread
when read and fread do the same thing more portably

cocoa is redoing the interfaces
and its much better
perhaps even better than traditional unix interfaces

i hope apple plans to put a cocoa interface for everyting

 > and if that doesn't work, the newer stuff can be found by the slower
 > recursive search of:
 >
 > /System/Library/Frameworks/

(find /System/Library/Frameworks -type f -print | xargs grep plover | more)

but still it misses some things

arf arf<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: quicktime - once more into the breech