• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Core Animation geometry, layer hosting, and resolution independence
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Core Animation geometry, layer hosting, and resolution independence


  • Subject: Re: Core Animation geometry, layer hosting, and resolution independence
  • From: Nathan Vander Wilt <email@hidden>
  • Date: Wed, 12 Mar 2008 17:06:52 -0500 (CDT)

> > CALayers don't have this bounds/frame distinction
>
> They do, actually. The bounds is the internal view
> of the coordinate
> system, and the frame is the external view.

At first this sounded incorrect, because it's
emphasized that frame is just a function of other
properties....but I was overlooking "transform" as one
of those. Interesting...not sure if this helps clear
the situation or not.

> > it almost seems
> > that 1 unit always corresponds to 1 pixel. How
> does
> > Core Animation's geometry relate to NSView's
> > resolution independent geometry?
>
> I think you're right about the pixels. That's news
> to me; I'm stumped.
> Hopefully some CA expert can enlighten us.

Despite the apparent help -[NSView
convertPointToBase:] gives, I'd still appreciate a
summary of the way all the many many CALayer
(/sublayer), NSView and Quartz context transformations
work together in light of resolution independence:

When one draws a rectangle in a CALayer delegate, and
the -drawLayer:: concatenates (and/or sets?) its own
transform before drawing, when the layer has a
transform, and the root parent layer has both a
transform and a sublayer transform, and the host
NSView has different bounds than frame, and there is
resolution independence / interface scaling.....*deep
breath*..... where/what order are all these transforms
applied to our brave rectangle victim. And between
what levels of all that does a (mouse, drawing, layer
origin) point need to be transformed for use, and how?

[As if that weren't confusing me enough, I'm actually
also applying a cartographic projection or three to
half of my source data...so being clear on the
Cocoa/Core Animation/Quartz interaction would help me
focus on just the map issues.]

thanks,
-natevw

__________________________________________________
Correo Yahoo!
Espacio para todos tus mensajes, antivirus y antispam ¡gratis!
Regístrate ya - http://correo.espanol.yahoo.com/
_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:

This email sent to email@hidden

  • Follow-Ups:
    • Re: Core Animation geometry, layer hosting, and resolution independence
      • From: Jens Alfke <email@hidden>
References: 
 >Re: Core Animation geometry, layer hosting, and resolution independence (From: Jens Alfke <email@hidden>)

  • Prev by Date: Re: Deleting a folder
  • Next by Date: Adding several UIViews in random places of the screen at intervals
  • Previous by thread: Re: Core Animation geometry, layer hosting, and resolution independence
  • Next by thread: Re: Core Animation geometry, layer hosting, and resolution independence
  • Index(es):
    • Date
    • Thread