> Apple's sample code Image Transition and Cocoa Slides both crash when built
> using Xcode 5.1 and run on 10.9.2
When built with 10.9 SDK, views using CIFilters need their
layerUsesCoreImageFilters set to YES.
Yeah, it bit me too...it's in the 10.9 release notes somewhere.
> But built apps
On Mar 31, 2014, at 11:17 AM, Kevin Meaney wrote:
> Apple's sample code Image Transition and Cocoa Slides both crash when built
> using Xcode 5.1 and run on 10.9.2. But built apps that apple provides with
> the sample code still work on 10.9.2. When built using Xcode 5.1 these
> samples crash
I think this problem might go beyond Core Animation, unless NSAnimation is
using CoreAnimation under the hood.
Apple's sample code Image Transition and Cocoa Slides both crash when built
using Xcode 5.1 and run on 10.9.2. But built apps that apple provides with the
sample code still work on 10.
> On Dec 3, 2013, at 5:23 AM, Graham Cox wrote:
>
> I’m seeing quite a few of these being logged:
>
>> CoreAnimation: warning, deleted thread with uncommitted CATransaction; set
>> CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.
>
> I’m not directly using Core Animation anywhere in
On Dec 3, 2013, at 10:23 PM, Graham Cox wrote:
> I’m seeing quite a few of these being logged:
>
>> CoreAnimation: warning, deleted thread with uncommitted CATransaction; set
>> CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.
>
> I’m not directly using Core Animation anywhere in thi
On Apr 16, 2013, at 9:40 PM, Ankuj Gupta wrote:
> The problem that I have is I cant change the apis for creating the windows.
> The only function which I can modify is when we are showing that window. That
> is where I need to animate it
What exactly is the animation that you need to show?
—
Hi Jens
The problem that I have is I cant change the apis for creating the windows.
The only function which I can modify is when we are showing that window.
That is where I need to animate it
Ankuj Gupta
On Tue, Apr 16, 2013 at 10:07 PM, Jens Alfke wrote:
>
> On Apr 16, 2013, at 5:10 AM, Anku
On Apr 16, 2013, at 5:10 AM, Ankuj Gupta wrote:
> Can we use Core Animation with NSWindow ? The apple's documentation
> mentions that we can use only with NSView. If there is any documentation
> for core animation used with NSWIndow
NSWindow doesn’t draw anything itself (aside from the window f
On Oct 26, 2011, at 4:20 AM, Brad Stone wrote:
> I understand there's an issue with focus rings not appearing in an editable
> cell if, like I do, you have an NSOutlineView sitting on a view that has Core
> Animation turned on.
I was under the impression that this was fixed on Lion. You should
On 2011-08-13, at 8:40 PM, William Squires wrote:
> Did you set a duration over which to animate? Also, if you return NO, won't
> the window NOT close after all, thus defeating the purpose of animating it
> disappearing? I believe you need to return YES after a synchronous operation
> which wi
On 2011-08-12, at 6:40 PM, Jens Alfke wrote:
>
> On Aug 12, 2011, at 3:19 PM, Izak van Langevelde wrote:
>
>> - (BOOL)windowShouldClose:(id)window{
>>
>>[self.window.animator setAlphaValue:0.0];
>>
>>return NO;
>> }
>>
>> The relevant view has its Core Animation Layer, as checked in
On Aug 12, 2011, at 3:19 PM, Izak van Langevelde wrote:
> - (BOOL)windowShouldClose:(id)window{
>
>[self.window.animator setAlphaValue:0.0];
>
>return NO;
> }
>
> The relevant view has its Core Animation Layer, as checked in X-Code, the
> above code is executed when I try to close a w
Perform the second transform after the first animation completes in a
separate animation block. You can start the second animation block
from the first animation block's completion block.
-Heath Borders
heath.bord...@gmail.com
Twitter: heathborders
http://heath-tech.blogspot.com
On Wed, Jun 1,
On May 17, 2011, at 2:58 PM, Kyle Sluder wrote:
> You could also try using -makeBackingLayer. That's useful if your view
> can be used both programmatically and in a nib.
I wonder if that method works for a layer-hosting view, which is what my view
is -- not a layer-backed view. But even if it
On Tue, May 17, 2011 at 11:35 AM, Bill Cheeseman wrote:
> I agree that the explanation doesn't logically lead to a prohibition on
> creating layers in -initWithFrame:. That's why I initially created them
> there, deferring only the construction of the layer tree to -awakeFromNib.
> But I suffer
On May 17, 2011, at 12:58 PM, David Duncan wrote:
> The basic problem comes about when a view in the nib has wantsLayer=NO, but
> the view itself always wants to be layer backed. If you setWantsLayer:YES
> inside of -initWithFrame:, then by the time you get to -awakeFromNib
> wantsLayer=NO aga
On Tue, May 17, 2011 at 10:21 AM, Keith Duncan wrote:
>
>> The basic problem comes about when a view in the nib has wantsLayer=NO, but
>> the view itself always wants to be layer backed. If you setWantsLayer:YES
>> inside of -initWithFrame:, then by the time you get to -awakeFromNib
>> wantsLay
> The basic problem comes about when a view in the nib has wantsLayer=NO, but
> the view itself always wants to be layer backed. If you setWantsLayer:YES
> inside of -initWithFrame:, then by the time you get to -awakeFromNib
> wantsLayer=NO again
Would there be any issue with overriding -setWa
On May 17, 2011, at 9:49 AM, Bill Cheeseman wrote:
> On May 17, 2011, at 11:33 AM, David Duncan wrote:
>
>> There should be no actual restriction like that however. That said, as you
>> point out, if you have view that supports layers and come from a nib, you
>> often have to duplicate work to
On May 17, 2011, at 11:33 AM, David Duncan wrote:
> There should be no actual restriction like that however. That said, as you
> point out, if you have view that supports layers and come from a nib, you
> often have to duplicate work to allow it to work in both situations.
I'm not sure I foll
On May 17, 2011, at 1:26 AM, Bill Cheeseman wrote:
> Answering my own question: Although it's hard to be sure that a random
> problem is really fixed, it appears that the solution was to stop creating
> Core Animation layers in the view's -initWithFrame: method and instead create
> them in the
On May 16, 2011, at 8:11 AM, Bill Cheeseman wrote:
> When I quit and relaunch the application, the animations sometimes don't run
> for the full specified duration when I hit the hot key. During any given run
> of the application, the animations either work correctly every time I hit the
> hot
On Mon, 16 May 2011 08:11:36 -0400, Bill Cheeseman said:
>My Mac OS X application has an borderless transparent overlay window with a
>layer-hosting view. The view's layers add a bunch of animations in response to
>a hot key. It all works correctly -- sometimes.
>
>What could account for sublaye
>> I'm not sure how you are detecting touches now, but you should look at
>> using CALayer's hitTest: method to determine if/what layer was
>> clicked/touched. If the animation is still moving, you definitely need
>> to be querying the presentationLayer and not the modelLayer.
>>
>>
> I am detectin
On Sat, Aug 21, 2010 at 5:32 PM, Eric Wing wrote:
> On 8/21/10, Ahsan Shafiq wrote:
> > Yes, you are right but now I am unable to handle touches.
> > As I said in my previous post, I also want to update the model. Simply
> > scaling as you mentioned does scale down or scale up the sublayers as
>
On 8/21/10, Ahsan Shafiq wrote:
> Yes, you are right but now I am unable to handle touches.
> As I said in my previous post, I also want to update the model. Simply
> scaling as you mentioned does scale down or scale up the sublayers as well
> but how to update the model. In Scaling both the posit
Yes, you are right but now I am unable to handle touches.
As I said in my previous post, I also want to update the model. Simply
scaling as you mentioned does scale down or scale up the sublayers as well
but how to update the model. In Scaling both the position and bounds get
changed!! and after an
> CABasicAnimation *animation =
> [CABasicAnimation animationWithKeyPath:@"bounds"];
> CGRect orgVal = CGRectMake(0, 0,
> firstWheelLayer.bounds.size.width, firstWheelLayer.bounds.size.height);
> CGRect newVal = CGRectMake(0, 0,
> firstWheelLayer.bou
bump*
On Thu, Aug 19, 2010 at 10:47 AM, Ahsan Shafiq wrote:
> Hi
> I have read that in explicit animation, say translation, to really change
> the model layer position we have to change it's position too. So here is my
> code:
>
> CABasicAnimation *animation =
> [CABasicAnimation
Le 1 juin 2010 à 21:02, Tino Rachui a écrit :
> THANKS David! I understand and got the code to run smoothly. Again one step
> towards understanding CA better, I'm happy. :)
OK, the same happened to me! My animations now run exactly as intended. The
EXC_BAD_ACCESS was due to the fact that I for
THANKS David! I understand and got the code to run smoothly. Again one step
towards understanding CA better, I'm happy. :)
@Rodolfo: If you are interested I can send you my complete little sample
project. Just let me know.
Regards,
Tino
Am 01.06.2010 um 19:08 schrieb David Duncan:
> On May 31
On May 31, 2010, at 11:51 PM, Tino Rachui wrote:
> I'm interested in this too so please excuse me for interfering. What is the
> root cause for Rodolfo's problem? He doesn't seem to set
> 'removedOnCompletion' to 'NO' (default is 'YES' according to docu) so I'm
> wondering if this could cause t
Hi Rodolfo,
2010/6/1 Rodolfo Niborski
>
> Neither I did figure out how to use David's code. I thought that overriding
> the implicit animation implies the use of layer actions. I can't see how
>
> [layer addAnimation:rotation forKey:@"transform"];
>
> can change the implicit animation.
>
Accordi
Hello,
Neither I did figure out how to use David's code. I thought that overriding the
implicit animation implies the use of layer actions. I can't see how
> [layer addAnimation:rotation forKey:@"transform"];
can change the implicit animation.
Besides, most of my attempts resulted in a EXC_BAD_A
David, Rodolfo,
I'm interested in this too so please excuse me for interfering. What is the
root cause for Rodolfo's problem? He doesn't seem to set
'removedOnCompletion' to 'NO' (default is 'YES' according to docu) so I'm
wondering if this could cause the unwanted effect (by the way I cannot see
David,
Thank you for your quick answer, I'll try this and let you know what happened.
By the way, I forgot to say that my question was on iPhone, but everything you
mention seems to be available in iPhone OS 3.0.
Rodolfo Niborski
http://itunes.com/apps/yiddishforkids1-alefbeys
Le 31 mai 2010 à
On May 31, 2010, at 2:24 PM, Rodolfo Niborski wrote:
> My problem is that at the end of the first animation, the "Hello" message
> shows up in its initial position for a fraction of a second.
> I've tried to set the fillMode of the first animation to kCAFillModeForwards
> with no effect.
What y
> There's a CoreAnimation sample project that does just this, called LightBoard.
> --Kyle Sluder
Thank you and thanks everyone else. I didn't find the LightBoard
sample but I found GeekGameBoard which helped me a lot.
John.
___
Cocoa-dev mailing list (
On Tue, Mar 16, 2010 at 5:16 AM, john fogg wrote:
> Photos need to be in layers as well so I can change the stacking
> order. Do I use CoreAnimation for this?
There's a CoreAnimation sample project that does just this, called LightBoard.
--Kyle Sluder
>
> So every photo needs to respond to mouse events. Do I make every photo
> into its own view? Or are views too expensive to create? I want to
> easily support 100+ photos or more. (I will downsample the images for
> performance.)
>
In my experience using many views for similar functionality dras
Am 12.03.2010 um 03:13 schrieb Mazen M. Abdel-Rahman:
> For the calendar grid I was creating an NSTrackingArea for each cell - in my
> case (the calendar is for 7 days with 15 minutes per cell) there was 672
> NSTrackingAreas.
>
> I will have to look at alternative solutions to all these NSTra
Hi Mazen, how are you?
Maybe I can offer a tip on how to improve your performance: there is a
technique called BSP-Tree which divides the space in two equal parts
recursively, creating a tree of subdivisions. This technique improves the
search of which area of the space (in your case, the view
Thanks everyone for your help on this.
I started using an image cache - but that did not improve the performance as
much as I thought it should. I then removed the section of my code that
creates NSTrackingsAreas - and the improvement was immediately noticeable.
For the calendar grid I was cre
Hi,
are you drawing ALL of your paths whenever the user scrolls or only the ones
that are within the visible rect? If the first, you may try to change that to
the second and gain lots of performance. I draw a sound wave view and when
drawing all of it while zoomed into it, it is sooowww. Bu
On 10 Mar 2010, at 17:13, Mazen M. Abdel-Rahman wrote:
> Hi All,
>
> I was able to write a simple calendar view that uses basic cocoa graphics to
> draw directly on the view (NSBezierPath, etc.). I actually use several
> different paths for drawing the calendar (it's a weekly calendar) to al
Well, I have found it to be even more weird. On Leopard, the Core
Animation animation sometimes can run simultaneously with the blocking
NSAnimation. In fact, I have done something to my app, don't know
what, and now CA runs in parallel with the blocking NSAnimation
causing the latter to jitter. I
On Sep 28, 2009, at 3:12 AM, Kyle Sluder wrote:
Do you mean I should avoid using blocking animations and only use
non-blocking? Never tried to use animator proxies, only NSAnimation
directly, so I don't know if the proxies are blocking or non-
blocking.
The animator proxies are related to Co
On Sun, Sep 27, 2009 at 11:38 PM, Oleg Krupnov wrote:
> Not sure I understand your idea and why it is bad. Could you elaborate?
Because it will cause delayed performs and other default-mode things
to execute when they might not expect to.
> Do you mean I should avoid using blocking animations an
Thanks,
> AppKit 10.6 release notes say that the core of the problem is that the
> animator proxy would run the animation in NSDefaultRunLoopMode. Now
> it's done in NSRunLoopCommonModes.
>
> I guess you could run the run loop once in NSDefaultRunLoopMode
> whenever you're running in a different
On Sun, Sep 27, 2009 at 10:51 PM, Oleg Krupnov wrote:
> Or is there a workaround, beside using non-blocking animation, which
> is often too tedious and sometimes not smooth enough?
AppKit 10.6 release notes say that the core of the problem is that the
animator proxy would run the animation in NSD
Thanks! You are right, I have tested it on Snow Leopard, and the CA
animation runs simultaneously with the blocking NSAnimation, as
claimed in the Wikipedia. What a revelation! I'd say, what an ANNOYING
revelation! It means that this ability of CA animation of running in a
separate thread is render
Take a look at this movie, which was taken on Leopard:
http://shlok.s3.amazonaws.com/20090927-ca-problem.mov
The blue rectangle is a layer-backed NSView that is animated using
Core Animation. The problem is that the animation halts while the main
loop waits for the mouse to get released.
Fo
Kyle,
I don't have a custom layer, I'm animating the transition between two
NSViews.
--
Evan
On Aug 23, 2009, at 4:24 PM, Kyle Sluder wrote:
On Aug 23, 2009, at 1:00 PM, Kevin Cathey wrote:
Have you enabled "wants layer" for the view?
And if you have, have you made sure to provide a c
Kevin,
Yes, wantsLayer is enabled.
--
Evan
On Aug 23, 2009, at 4:00 PM, Kevin Cathey wrote:
Have you enabled "wants layer" for the view?
Kevin
--
Kevin Cathey
On 22 Aug 2009, at 22:21, Evan M wrote:
So, it isn't Garbage Collection + Core Animation that is breakin
On Aug 23, 2009, at 4:34 PM, Rob Keniger wrote:
Why's that? It seems to work fine in all my testing.
There are cases where it breaks.
Providing your own layer is the defining difference between a layer-
backed and a layer-hosting view. AppKit makes certain assumptions
about the underlying
On 24/08/2009, at 6:24 AM, Kyle Sluder wrote:
Have you enabled "wants layer" for the view?
And if you have, have you made sure to provide a custom layer
*before* calling -setWantsLayer:? The default AppKit provided layer
is Not Yours to touch.
Why's that? It seems to work fine in all m
On Aug 23, 2009, at 1:00 PM, Kevin Cathey wrote:
Have you enabled "wants layer" for the view?
And if you have, have you made sure to provide a custom layer *before*
calling -setWantsLayer:? The default AppKit provided layer is Not
Yours to touch.
--Kyle Sluder
___
Have you enabled "wants layer" for the view?
Kevin
--
Kevin Cathey
On 22 Aug 2009, at 22:21, Evan M wrote:
So, it isn't Garbage Collection + Core Animation that is breaking
the transition, I just refactored my entire project to remove GC
support (big pain) and the
So, it isn't Garbage Collection + Core Animation that is breaking the
transition, I just refactored my entire project to remove GC support
(big pain) and the animation hasn't changed at all.
Now I'm looking at my custom NSView that is being animated and I'm
wondering now if that is the prob
On Aug 19, 2009, at 10:54 AM, Evan Moseman wrote:
I've been trying to get a fairly simple and well documented
transition: CIPageCurlTransition to work in my app, but the results
are awful. Non filter transitions like kCATransitionFade work fine,
but when I try to use a CAFilter for the tra
On Jul 23, 2009, at 1:15 AM, David Duncan wrote:
On Jul 22, 2009, at 10:05 PM, Randall Meadows wrote:
Any idea why the drawing is screwing up for the 2nd animation? Are
the 2 different methods of animating messing up each other somehow
(even though I've removed the 1st animation)?
This i
On Jul 22, 2009, at 10:05 PM, Randall Meadows wrote:
newBounds.origin.x -= delta/2.0;
newBounds.size.width += delta;
newBounds.origin.y -= delta/2.0;
newBounds.size.height += delta;
BTW, you might want to look up the NSInsetRect() function.
-jcr
___
On Jul 22, 2009, at 10:05 PM, Randall Meadows wrote:
Any idea why the drawing is screwing up for the 2nd animation? Are
the 2 different methods of animating messing up each other somehow
(even though I've removed the 1st animation)?
This is working as expected (for the default case at lea
Resending this because my browser messed up the formatting, apologies
Hi all. I had some previous questions about Core Animation, this is not
related to that at all (so don't take the previously mentioned code and
methods into consideration).
I have a transparent window, in which I create a vi
It's not really clear what you are asking. Your final question is
"Does this sound correct?" to which I would respond, "yes". Though
earlier in the message you ask for advice on the "remaining parts".
It would help if you were to clarify what you mean. When you say "...a
miracle happens...(
On Feb 4, 2009, at 7:27 AM, Nick Brandaleone wrote:
I am creating a simple search app, and I want to "highlight" the
found word/phrase in a large body of text,
in a similar way that Safari does it (background goes dim, and word
is highlighted).
Would NSTextView -showFindIndicatorForRange:
Thank you Scott. I will re-read the introduction ... My speed reading
techniques may have failed me!
On Jan 23, 2009, at 3:26 PM, Scott Anguish wrote:
Core Animation handles the threading aspects of this automatically.
The introduction should have been clear about it (if not, file a
bug w
Core Animation handles the threading aspects of this automatically.
The introduction should have been clear about it (if not, file a bug
with what was unclear)
On 23-Jan-09, at 5:20 PM, David Blanton wrote:
I have gone over the CA docs ... a quick read.
I have an iPhone app that uses the
On Nov 22, 2008, at 11:41 AM, Wolf Hauser wrote:
Question: is there a (simple) way to switch all these implicit
behaviors off (while keeping the possibility to stack the two views
in layers)?
Since this doesn't appear to have been answered, there is a long
mechanism that determines what
Got it. Thanks for the clarification.
-Matt
On Nov 23, 2008, at 6:29 AM, Michael Ash wrote:
On Sun, Nov 23, 2008 at 12:46 AM, Matt Long <[EMAIL PROTECTED]
> wrote:
Ok. This is interesting. I wrote a little code to see what might be
going
on.
Whatever was true when the AppKit release notes
On Sun, Nov 23, 2008 at 12:46 AM, Matt Long <[EMAIL PROTECTED]> wrote:
> Ok. This is interesting. I wrote a little code to see what might be going
> on.
>
> Whatever was true when the AppKit release notes were published has either
> changed or the term "supported" has a loose definition. Thanks for
Thank you both for your great support. Obviously, "not presently
supported" does not mean it raises an exception when you try to do it
anyway (otherwise I would have noticed) -- it probably just means that
you are likely to run into quirks, which is exactly what happened to me.
But now I ha
Ok. This is interesting. I wrote a little code to see what might be
going on.
Whatever was true when the AppKit release notes were published has
either changed or the term "supported" has a loose definition. Thanks
for pointing that out, Mike, but I don't think it's accurate or I've
misun
On Sat, Nov 22, 2008 at 2:41 PM, Wolf Hauser <[EMAIL PROTECTED]> wrote:
> Hello,
>
> Background: the application I am trying to build consists mainly of a
> WebView. And I need to perform some custom drawing in front of that WebView.
> First, I simply placed (in IB) a custom view in front of the We
Hi Matt,
thank you for your help.
[CATransaction begin];
[CATransaction setValue:(id)kCFBooleanTrue
forKey:kCATransactionDisableActions];
// Your code here
[CATransaction commit];
I had tried to use this, however I was not sure where to put it. My
problem is with the "Your c
Have you tried :
[CATransaction begin];
[CATransaction setValue:(id)kCFBooleanTrue
forKey:kCATransactionDisableActions];
// Your code here
[CATransaction commit];
See also:
http://developer.apple.com/documentation/Cocoa/Conceptual/CoreAnimation_guide/Articles/Transactions.html
CATransform3D transform = CATransform3DMakeScale(factor, factor,
factor);
[mainLayer setTransform:transform];
[mainLayer setOpacity:0.0];
The layer instead gets *scaled* by the factor you specify.
I tried this, and it works fine as far as smooth animation is
concerned. The problem though i
I can't speak to the example you mention specifically, but I had tried
to scale font sizes this way as well and never got the smooth
transition either. Instead I used something like this:
CATransform3D transform = CATransform3DMakeScale(factor, factor,
factor);
[mainLayer setTransform:tran
Hi,
I am in the same boat. I have an NSTextView inside an NSScrollView
that shows the default transitions when new text is added, or when the
scroll view is resized. I don't want that.
However, I can't figure out where to override the default transition.
I subclassed both the NSTextView an
Am Jun 30, 2008 um 07:04 schrieb Papa-Raboon:
I was wondering if many of you have had a go at core animation yet?
I am personally looking at making a piece of text fade in and fade
out as a
confirmation that something worked in my latest project. Currently I
am just
popping a bit of text on
Text is tricky because of the anti-aliasing issues.
Broaden your search though there are tons of examples on how to fade a
layer in and out of a scene (apple's samples, my blog, others as well).
Basically though
- parent view needs to be layer backed (via setWantsLayer:YES)
- create a layer
All default (implicit) animations are returned in the method:
+(id)defaultAnimationForKey:(NSString*)key
You can simply override this and just return nil. This would mute out
all implicit animations.
And if you want specific animations, you can set them into the
animations dictionary of th
at the core animation level...
three options
1: disable actions in a explicit transaction and do everything inside
that transaction
http://developer.apple.com/documentation/Cocoa/Conceptual/CoreAnimation_guide/Articles/Transactions.html#/
/apple_ref/doc/uid/TP40006096-SW9
or 2:http://deve
Just an update on this issue...
Everything looked fine in the console when I enabled that debug
switch. However, I've sidestepped the issue and created an alternate
implementation that does not flicker. Drawing manually in a CALayer
had other challenges, such as not doing synchronized drawi
On Apr 25, 2008, at 1:20 AM, Colin Cornaby wrote:
I have a CALayer subclass, set to redraw on bounds change, with the
following draw code (I don't expect it to be meaningful, but I'm
pasting it here for the sake of completeness.)
…
It's parent view is set up to change the layers frame to al
I may have the bug isolated. I fixed a bug in my own code, and the
deadlock is no longer happening. It may be related to a situation
involving removing a sublayer from it's super. In my code I was
removing a layer that I didn't intend to remove, and the deadlock
would result.
I still thin
Enabled NSZombie and friends didn't seem to fix the issue (or log
anything.)
This isn't going to be too easy to track down. Once I figure out what
series of events is triggering it I will try to put together a test
case.
On Apr 24, 2008, at 9:14 PM, John Harper wrote:
On Apr 24, 2008,
On Apr 24, 2008, at 7:38 PM, Colin Cornaby wrote:
It looks like NSUIHeartBeat could be attempting to lock something.
Although I could be wrong, it may not be related.
The render thread got stuck while depth sorting:
Thread 11 (process 13823 thread 0x8803):
#0 0x90a27d9c in CARenderLayerDe
It looks like NSUIHeartBeat could be attempting to lock something.
Although I could be wrong, it may not be related.
Here's the full stack trace across all threads.
(gdb) thread apply all bt
Thread 37 (process 13823 thread 0xf11b):
#0 0x958af506 in semaphore_timedwait_signal_trap ()
#1 0x95
You could also show any other thread stuck trying to lock a mutex? I
assume there's another thread holding this lock or stuck trying to lock
something else.
Colin Cornaby wrote:
Hi,
I'm currently trying to track down a deadlock. After adding a series
of layers, CoreAnimation deadlocks here
On Apr 16, 2008, at 6:49 PM, Karl Goiser wrote:
I'm creating a borderless window whose content view uses Core
Animation...
When I do this, the window is drawn without any shadow no matter the
alpha of the content.
- a borderless window with a normal view draws the window's shadow.
- a no
Hi Matt,
I hope what Scott said made sense (and what I said in the book, thanks
BTW to Mike for the plug).
If you have a layer backed view (i.e. you only call
myButton.wantsLayer = YES) then you should not ever touch the layer,
only use the methods that are exposed through the view and it
don't work with the layer directly when you have layer-backed views
only do it when you are using layer-hosting views
On Apr 8, 2008, at 8:30 AM, Manfred Schwind wrote:
Hi,
I have a layer-backed NSView, say an NSButton (or a complete view
hierarchy with many controls), and I am transformi
Hey Mani,
I never solved the problem completely, however, I realized that what
you need to do, or so it seems, is to somehow get notified when the
animation has finished and then actually move the button to the
position where the animation stopped. It seems really convoluted to
me, but I
From "Core Animation for OS X", by Bill Dudney:
"Since the view is managing the layer and has to be intimately
familiar with what is going on with the layer it is not recommended
that we manipulate the layer in any way except through the methods
exposed through the view. As long as we use t
> I have a situation where I want to re-order
> sublayers of a layer which
> are positioned using CAConstraints.
>
> Is this at all possible?
Not sure what you mean by "re-order", whether z-order
or sibling order, or if you mean re-layout? Using
CAConstraints will help with the last option.
>
As far as i know, you can either set the constraints property to nil
and re-set the constraints you want to use, or set up your own layout
manager to handle positioning the layers.
On Mar 13, 2008, at 4:23 PM, Karl Goiser wrote:
Hello Cocoaers,
I have a situation where I want to re-order s
--- 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
1 - 100 of 108 matches
Mail list logo
