After much (private) talk with David, we are both at the loss with this issue.
I'll investigate further but, meanwhile, does somebody here on the list have
tried to refresh CALayer within GCD blocks? If yes, does it work?
Thanks,
Vincent___
Cocoa-dev
David,
Yes. I have put a NSLog in both -display and -drawInContext. The first is run,
the second never...
Vincent
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the
On Sep 3, 2010, at 7:50 AM, Vincent Habchi wrote:
>> I have implemented what you suggested. I get a strange behavior: the first
>> time I enqueue a request for display, everything is fine. But then I cannot
>> draw any further: any subsequent call, albeit correctly enqueued in the
>> block, doe
> I have implemented what you suggested. I get a strange behavior: the first
> time I enqueue a request for display, everything is fine. But then I cannot
> draw any further: any subsequent call, albeit correctly enqueued in the
> block, does nothing: the -(void)display
Read: "at any subsequen
Le 3 sept. 2010 à 00:17, David Duncan a écrit :
> Doing so would cause you all manners of pain and suffering, the most common
> of which is things "mostly" working but occasionally your drawing going into
> the wrong view. Basically *never* use the context given to you in
> -drawInContext: outs
On Sep 2, 2010, at 3:17 PM, David Duncan wrote:
> On Sep 2, 2010, at 11:29 AM, vincent habchi wrote:
>
>> You mean I shall use your dispatch_async invocation instead of calling
>> [layer setNeedsDisplay]?
>
> Calling -setNeedsDisplay arranges for -display to later be called on the
> current r
On Sep 2, 2010, at 11:29 AM, vincent habchi wrote:
> You mean I shall use your dispatch_async invocation instead of calling [layer
> setNeedsDisplay]?
Calling -setNeedsDisplay arranges for -display to later be called on the
current runloop. As such using -setNeedsDisplay is reliant on a runloop
Hi Vincent,
On 2 Sep 2010, at 11:29 AM, vincent habchi wrote:
> I promise I did not plan to start an Apple internal quarrel! ;)
I don't think there's any real quarrel here; David and I are looking at this
from two distinct points of view. :)
The docs for +[CATransaction flush] make the stateme
David, Chris,
I promise I did not plan to start an Apple internal quarrel! ;)
>>> dispatch_async(queue, ^{
>>> [layer display];
>>> [CATransaction flush];
>>> }
>>
>> There is (almost) never any reason for anyone to be calling +[CATransaction
>> flush] directly. You'll cause all sorts o
On Sep 2, 2010, at 9:40 AM, Chris Parker wrote:
> On 2 Sep 2010, at 8:52 AM, David Duncan wrote:
>
>> On Sep 2, 2010, at 7:39 AM, Vincent Habchi wrote:
>>
>>> I just wanted to know someone has already tried to successfully send a
>>> CALayer -drawInContext method to a GCD dispatch queue. I susp
On 2 Sep 2010, at 8:52 AM, David Duncan wrote:
> On Sep 2, 2010, at 7:39 AM, Vincent Habchi wrote:
>
>> I just wanted to know someone has already tried to successfully send a
>> CALayer -drawInContext method to a GCD dispatch queue. I suspect this is not
>> possible, because of main loop relat
On Sep 2, 2010, at 7:39 AM, Vincent Habchi wrote:
> I just wanted to know someone has already tried to successfully send a
> CALayer -drawInContext method to a GCD dispatch queue. I suspect this is not
> possible, because of main loop related issue, but this is unclear.
This can be done, but y
Hi everybody,
I just wanted to know someone has already tried to successfully send a CALayer
-drawInContext method to a GCD dispatch queue. I suspect this is not possible,
because of main loop related issue, but this is unclear.
If it does not work, does it make sense to divide the code in two
13 matches
Mail list logo
