On 31/01/2007 07:08 Pm, Eric Schlegel wrote:
> The plugin case is actually a good example of why saving and
> restoring the gstate really is the better way to go.
>
> Your comment is that the context might have a non-identity CTM on
> entry to the plugin, and therefore saving and restoring the CTM won't
> get you back to identity. But typically, you wouldn't _want_ to get
> back to identity in that case. The CTM has been set up by the host
> application in whatever way that the host app deems appropriate.
> Maybe the host app is displaying a magnified view of the plugin
> content so it's passing in a CTM with a 2x magnification. If you
> revert all the way back to an identity matrix, you'll lose the
> magnification. You really want to revert back to the CTM state that
> the host app provided.
Good point. BTW, Steve didn't told us *why* does he need
identity matrix...
> As far as setting up other context values, if you save the CTM state
> right at entry, then any changes to CTM state have been applied by
> code that you called. You should be able to call that code again.
Mike
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
This email sent to email@hidden
