On Apr 30, 2013, at 18:37 , Gideon King wrote:
> How did you test it? Did you sort the views at all, or just leave them in the
> order they were instantiated?
My hierarchy is very simple. The content view contains a single view (which
layer-backed in order to use a background color), and that
How did you test it? Did you sort the views at all, or just leave them in the
order they were instantiated? Did you try Sean's workaround?
Regards
Gideon
On 01/05/2013, at 4:39 AM, Quincey Morris
wrote:
>
> Nope. I just tried it again, setting the layer-backed checkboxes all the way
>
On Apr 30, 2013, at 08:55 , Mike Abdullah wrote:
> On 30 Apr 2013, at 16:53, Gideon King wrote:
>
>> So it sounds as if as long as I have all my views in the entire hierarchy
>> layer backed, my sibling views should always draw in order.
>
> Yup. Bear in mind WebViews don't support being lay
On Tue, 30 Apr 2013 01:30:00 -0700, Quincey Morris said:
>On Apr 30, 2013, at 00:39 , Gideon King wrote:
>
>> My scenario is a whole lot of sibling, potentially translucent,
>overlapping, layer backed views.
>
>I've never seen any evidence that sibling *NSView*s draw in the wrong
>order since 10.
On 30 Apr 2013, at 16:53, Gideon King wrote:
> So it sounds as if as long as I have all my views in the entire hierarchy
> layer backed, my sibling views should always draw in order.
Yup. Bear in mind WebViews don't support being layer-backed (still!), which can
throw a spanner in the works.
So it sounds as if as long as I have all my views in the entire hierarchy layer
backed, my sibling views should always draw in order.
This makes me happy :) … and the documentation wrong :( - I'll report that.
Regards
Gideon
___
Cocoa-dev maili
On Tuesday, 30. April 2013 at 10:42, Mike Abdullah wrote:
> Layer-backed views always *appear* above non-layer-backed views. Effectively,
> all non-layer-backed views get rendered into a single layer that makes up the
> entire window.
Thanks, didn't know this. Never needed layer backed view unti
On 30 Apr 2013, at 09:38, Robert Vojta wrote:
>> I've never seen any evidence that sibling *NSView*s draw in the wrong order
>> since 10.5. I believe that 'drawRect:' is correctly called in the
>> back-to-front order of the sibling arrangement in the parent view.
>>
>> However, I *have* seen
> I've never seen any evidence that sibling *NSView*s draw in the wrong order
> since 10.5. I believe that 'drawRect:' is correctly called in the
> back-to-front order of the sibling arrangement in the parent view.
>
> However, I *have* seen firsthand, in the last few weeks, that the layers of
On Apr 30, 2013, at 00:39 , Gideon King wrote:
> My scenario is a whole lot of sibling, potentially translucent, overlapping,
> layer backed views.
I've never seen any evidence that sibling *NSView*s draw in the wrong order
since 10.5. I believe that 'drawRect:' is correctly called in the back
The docs are out of date. Overlapping views work properly as of 10.5 (albeit
you might run into performance problems if you push it too far). Please use the
feedback thing on the bottom of the docs to let Apple know it's wrong!
On 30 Apr 2013, at 08:39, Gideon King wrote:
> Hi, I had to design
11 matches
Mail list logo
