forgot to click reply all From: edward taffel <etaf...@me.com> Subject: Re: NSScroller revision? Date: April 28, 2014 at 11:08:23 AM EDT To: Kyle Sluder <k...@ksluder.com>
kyle, i believe you are correct, but not for any release on my side. thanks again for your insight. & just in case anyone was following this thread: as initWithFrame appeared the culprit for the vertical scroller, i changed initWithFrame to simple init & the issue resolved; apparently, horizontal is the NSScroller default—i got two horizontal scrollers, & reframing alone does not get a vertical from a horizontal. the only way i have discovered to get a vertical from NSScroller is to initialize with width > height; so, i had been initializing w/ width 100 for vertical & height 100 for horizontal, later (re)framing both to requisite extent. reframing a vertical seems to engender the _updateLayerGeometry & consequent ‘deleted thread with uncommitted CATransaction’, which does not apparently occur for the default (horizontal) case. i now create both scrollers initializing w/ requisite frame, at a later point after exact view dimensions are determined: the issue is gone. apparently, reframing vertical scrollers is now potentially problematical in some contexts. On Apr 25, 2014, at 4:16 PM, edward taffel <etaf...@me.com> wrote: > On Apr 25, 2014, at 3:32 PM, Kyle Sluder <k...@ksluder.com> wrote: > >> On Fri, Apr 25, 2014, at 12:20 PM, edward taffel wrote: >>> i just noticed & i’m not sure in which seed it occurred: NSScroller seems >>> to have undergone some revision. i now get this message: >>> >>> CoreAnimation: warning, deleted thread with uncommitted CATransaction; >>> created by: >>> 0 QuartzCore 0x00007fff96328ff6 >>> _ZN2CA11Transaction4pushEv + 312 >>> 1 QuartzCore 0x00007fff96328b29 >>> _ZN2CA11Transaction15ensure_implicitEv + 273 >>> 2 QuartzCore 0x00007fff963289c6 >>> _ZN2CA11Transaction9set_valueEj12_CAValueTypePKv + 40 >>> 3 QuartzCore 0x00007fff9632895a >>> +[CATransaction setDisableActions:] + 38 >>> 4 AppKit 0x00007fff94005985 >>> -[NSScrollerImp _updateLayerGeometry] + 68 >>> 5 AppKit 0x00007fff94004f52 >>> -[NSScroller(NSInternal2) _replaceScrollerImp] + 401 >>> 6 AppKit 0x00007fff94164647 -[NSScroller >>> initWithFrame:] + 391 >>> ... >>> >>> the message is logged about 10 seconds after launch, once for the >>> vertical scroller only; the scroller looks & behaves as expected. both >>> scrollers are programmatically added (not in ib). >>> >>> does anyone have any idea what the issue is? >> >> Often times this happens if an instance of a layer-backed NSView (of >> which NSScroll is an example) is deallocated on a background thread. >> >> Ensure that the last reference to your views is always released from the >> main thread. >> >> --Kyle Sluder > > thanks kyle, > > if this were the case, i should expect to see the same report for both > scrollers; as they are allocated & released at the same code points, & i > don’t pass the references around. but, i’ll do some checking to be sure. > _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
