Re: rendering destination dimensions bug?

Subject: Re: rendering destination dimensions bug?

From: Alessandro Sabatelli <email@hidden>

Date: Fri, 2 Dec 2005 14:54:25 -0500

Delivered-to: email@hidden

Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=GvKEkXSHjhmh4DnkZIJws5uoQ/n73Dh/UtTcyIFX8LXYl9Rz8omaFgf2o00PBgOYrlvpF4nJ4WR8+YqnDKizc3NA/Z2cTC5mOup8KTJ7bfJvPbfTo5gAAtzVEE6JvgtVsb9WvxTsYJ9sVstpb7m34DGbYJYeFstQoDkuPO76a2Y=

On 11/29/05, Roger Bolton <email@hidden> wrote:

> > is there currently a known bug with rendering destination
> > dimensions not updating correctly
> > when in full screen mode?
>
> does this happen in the QC editor or a custom app?

In the QC editor. I've managed to narrow down this bug.  I have a macro
that gets enabled that does a "render in image" set to size 0x0 (so
render at screen dimensions).  when the macro first gets enabled
a "rendering destination dimensions node is not reporting the correct
size until I drag to resize the window.

I have to say I find it very frustrating that render in image and core
image accumulator don't let you specify the rendering size through
inputs.  I usually want to render at the same resolution as a source
quicktime but there's no easy way of doing that at the moment.

Thanks

Roger
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartzcomposer-dev/email@hidden

This email sent to email@hidden

_______________________________________________ Do not post admin requests to the list. They will be ignored. Quartzcomposer-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/quartzcomposer-dev/email@hidden This email sent to email@hidden