>When assigning images to members from the memory buffer, Director
>automatically creates a duplicate of the image.
Ok, I've verified that:
new(#bitmap)
imgA = image(320, 240, 32)
put imgA
--
put member(1).image
--
member(1).image = imgA
put member(1).image
--
> However, when reversing the
>I think the stage image is of a different class than a member image- more
>housekeeping is done with the latter, etc.
It appears you're right on that--I just ran some tests, and member image
assignment does not work the same way.
Cordially,
Kerry Thompson
[To remove yourself from this li
At 10:37 AM -0700 6/8/01, Kerry Thompson wrote:
>>I wouldn't think so. If you then change pDotSprite.member.image,
>>hiliteImage is not changed (afaik),
>> so images are not passed by reference like lists- at least when
>>you specify then as a member image.
>
>Wow--we found something we can d
>I wouldn't think so. If you then change pDotSprite.member.image,
>hiliteImage is not changed (afaik),
> so images are not passed by reference like lists- at least when you
> specify then as a member image.
Wow--we found something we can disagree on :-)
Check this out:
-- Welcome to Directo
Hi Kerry,
When assigning images to members from the memory buffer, Director
automatically creates a duplicate of the image. However, when reversing the
process, i.e. if you assign the image of a member to an image object, thats
when a pointer is used.
Heres what the message window had to say:
-
At 7:05 PM -0700 6/7/01, Kerry Thompson wrote:
>I've created an image in memory with imaging lingo. In the debugger,
>it shows up as:
>
>hiliteImage =
>
>When I do this:
>
>pDotSprite.member.image = hiliteImage
>
>the watch window shows that member as:
>
>pDotSprite.member.image =
>
>The image
I've created an image in memory with imaging lingo. In the debugger, it
shows up as:
hiliteImage =
When I do this:
pDotSprite.member.image = hiliteImage
the watch window shows that member as:
pDotSprite.member.image =
The image is just a pointer. Shouldn't the member's image be the same a
