Great. The errors were 576 at the beginning. Now they are only 20...
The porting continues. Maybe you know this too:
I can't longer use the APIs from QTMovie.h
IsMovieDone
MoviesTask
SetMovieDrawingCompleteProc
SetMovieGWorld
UnlockPixels
Do you know how to replace them?
I am porting everything to the new QTMovie class but these APIs above seem
to not have an equivalent there. I already asked to the QT list, still
waiting for a reply. So I ask here, which is a more responsive list.
--
Leo
> Da: Clark Cox <clarkc...@gmail.com>
> Data: Tue, 15 Dec 2009 07:27:41 -0800
> A: "gMail.com" <mac.iphone....@gmail.com>
> Cc: Ken Thomases <k...@codeweavers.com>, <cocoa-dev@lists.apple.com>
> Oggetto: Re: memcpy with 64 bit
>
> On Tue, Dec 15, 2009 at 6:33 AM, gMail.com <mac.iphone....@gmail.com> wrote:
>> Thanks,
>> I have just read that doc
>> http://developer.apple.com/mac/library/documentation/Performance/Conceptual/
>> ManagingMemory/Articles/MemoryAlloc.html
>>
>> So it seems I can really calloc e.g. 60MB with calloc. Can you confirm?
>
> Yes, why wouldn't you be able to?
>
>> If not, I could use NSMutableData. If so, could I get the pointer with this?
>> imageBase = [data bytes];
>
> You would want to use [data mutableBytes].
>
>> If I use calloc, then when I call free(ptr) does the memory get release
>> immediately?
>
> Yes.
>
>> Or does it behave as I call [data release]; ?
>>
>> --
>> Leo
>>
>>> Da: Ken Thomases <k...@codeweavers.com>
>>> Data: Tue, 15 Dec 2009 04:50:07 -0600
>>> A: "gMail.com" <mac.iphone....@gmail.com>
>>> Cc: <cocoa-dev@lists.apple.com>
>>> Oggetto: Re: memcpy with 64 bit
>>>
>>> On Dec 15, 2009, at 2:50 AM, gMail.com wrote:
>>>
>>>>> Da: Andrew Farmer <andf...@gmail.com>
>>>>> Data: Mon, 14 Dec 2009 20:17:41 -0800
>>>>>
>>>>> On 14 Dec 2009, at 11:06, gMail.com wrote:
>>>>>> Handle imagesH = NewHandleClear(totImages * oneImageSize);
>>>>>
>>>>> Wait, Handle? NewHandleClear? Your use of these functions suggests
>>>>> that you
>>>>> may be working from a dangerously old textbook. There's really no
>>>>> reason to
>>>>> use them in new code.
>>>>
>>>> Ouch! That's my old code. But it works on
>>>> 64-bit Intel, Base SDK 10.6, x86_64, GCC 4.2, Target Mac OS X 10.6
>>>> I need an handle to store image bitmap data for later reuse by the
>>>> OpenGL
>>>> API "glTexImage2D". Do you know a better way?
>>>
>>> There's no good reason why it has to be a handle. Use an
>>> NSMutableData or even just malloc a chunk of the heap.
>>>
>>> Handles have an unnecessary level of indirection. Back in the day,
>>> that came with relocatability, but it doesn't anymore. It's just
>>> obscure and excessively complicated.
>>>
>>> Regards,
>>> Ken
>>>
>>
>>
>> _______________________________________________
>>
>> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>>
>> Please do not post admin requests or moderator comments to the list.
>> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>>
>> Help/Unsubscribe/Update your Subscription:
>> http://lists.apple.com/mailman/options/cocoa-dev/clarkcox3%40gmail.com
>>
>> This email sent to clarkc...@gmail.com
>>
>
>
>
> --
> Clark S. Cox III
> clarkc...@gmail.com
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
