> of 800x480 (as opposed to my iPhone's 480x320 pixel size), and the two
> together got me thinking more seriously about resolution independence again.
> Other than making big icons for my apps, I had pretty much ignored the
> resolution independence issue.
>
> Today
nd the two together
got me thinking more seriously about resolution independence again. Other than
making big icons for my apps, I had pretty much ignored the resolution
independence issue.
Today I fired up Quartz Debug to set the UI Resolution to a bigger scale, and I
am happy that my applic
--- Jens Alfke <[EMAIL PROTECTED]> escribió:
>
> On 12 Mar '08, at 2:49 PM, Nathan Vander Wilt wrote:
>
> > I don't understand what this "base" coordinate
> system
> > is (not the window's, otherwise the conversions
> would
> > likely be offset by the view's position therein,
> > right?). But w
On Mar 12, 2008, at 14:49, Nathan Vander Wilt wrote:
I don't understand what this "base" coordinate system
is (not the window's, otherwise the conversions would
likely be offset by the view's position therein,
right?). But whatever it is, it seems to be shared by
the CALayer. I'd appreciate a g
On 12 Mar '08, at 2:49 PM, Nathan Vander Wilt wrote:
I don't understand what this "base" coordinate system
is (not the window's, otherwise the conversions would
likely be offset by the view's position therein,
right?). But whatever it is, it seems to be shared by
the CALayer.
The Cocoa Drawi
, and the host
NSView has different bounds than frame, and there is
resolution independence / interface scaling.*deep
breath*.
This is starting to sound like "Fox In Socks"[1]:
"When tweetle beetles battle with paddles in a puddle,
they call it a tweetle beetle puddle paddle
f 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
--- Quincey Morris <[EMAIL PROTECTED]>
escribió:
> On Mar 12, 2008, at 13:13, Jens Alfke wrote:
>
> > On 12 Mar '08, at 12:13 PM, Nathan Vander Wilt
> wrote:
> >
> >> I want to be able to convert a mouse
> >> coordinate into a point suitable for
> -hitTest:'ing on
> >> my root layer. I can convert
On Mar 12, 2008, at 13:13, Jens Alfke wrote:
On 12 Mar '08, at 12:13 PM, Nathan Vander Wilt wrote:
I want to be able to convert a mouse
coordinate into a point suitable for -hitTest:'ing on
my root layer. I can convert from the mouse
coordinates to the view's coordinates, but then I am
not su
On 12 Mar '08, at 12:13 PM, Nathan Vander Wilt wrote:
I want to be able to convert a mouse
coordinate into a point suitable for -hitTest:'ing on
my root layer. I can convert from the mouse
coordinates to the view's coordinates, but then I am
not sure how to proceed.
There doesn't seem to be a
I am having trouble understanding how Core Animation
geometry interacts with NSView geometry in a
layer-hosting situation.
I have an NSView that hosts a root layer, and it has
two sublayers that I need the user to be able to drag
each around. I want to be able to convert a mouse
coordinate into a
11 matches
Mail list logo
