site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com On Aug 27, 2008, at 6:07 PM, ben syverson wrote: Do you absolutely need to access the point value during frameCleanup? - ben On 27 août 08, at 19:01, Garrick Meeker wrote: _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/garrick%40digitalanarchy... _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.ap... frameCleanup is when it works as I'd expect. It's renderOutput that's giving weird results. I've found that there are certain parts of the API that don't necessarily work as expected in some methods. It would be nice if they simply returned an error instead of returning strange values, but it's not a huge deal if you know what works where. Here's my printf's showing x and y from getXValue, x and y scale, width, and height. The odd lines are from renderOutput and the even lines (that around about 0.5) are from inside frameCleanup. It's applied to a simple rectangle shape that covers about half of a DV frame. Does this make any sense? This email sent to garrick@digitalanarchy.com This email sent to site_archiver@lists.apple.com