I have an intermittent crasher that appears to be associated with
IKImageBrowserView, but I have been unable to find a technique to get to the
source of the problem.
I have a dozen crash reports from the last month from beta testers of
PhotoLinker, which now uses ARC. The crash reports all poin
I've hunted around an it's not clear to me whether or not an NSOperation
instance strongly or weakly references its dependencies. Does anybody know the
answer?
An NSOperationQueue strongly references the operations in its queue (which
makes sense). It would also seem to make sense to have an NS
Much thanks to the three of you for your responses, with your help I was able
to solve the problem. It was a dumb mistake on my part that was exposed due to
different behavior in how dyld works (apparently?!).
I have dependencies on a bunch of my own frameworks, and a few third party
frameworks
I just transitioned my (primarily Cocoa based) code from building 32-bit
i386/PPC, to also include x86_64. Unfortunately, when launching the 64-bit
version I'm getting a crash at launch and I can't figure out how to debug it.
Stack trace at the bottom of the email.
- The crash does *not* occur
On Mar 26, 2010, at 11:31 AM, Jens Alfke wrote:
>
> On Mar 26, 2010, at 7:40 AM, Jeffrey J. Early wrote:
>
>> They actually don't have to be inside the library bundle... there's an
>> "Advanced" preference to not copy the original into the library.
&
easily made a bad assumption about something
> else and were trying to fix it in the drag.
>
> And if you would like to see a new OS or application feature, file a bug at
> <http://bugreport.apple.com/>. Just grousing about it here will not effect
> change within Apple.
>
On Mar 26, 2010, at 10:23 AM, Jens Alfke wrote:
>
> On Mar 26, 2010, at 7:00 AM, Jeffrey J. Early wrote:
>
>> When a user drags a photo from iPhoto to my application I need to be able to
>> update iPhoto's database (via ScriptingBridge) with changes that are ma
should it matter?
>
> Matt Gough
>
> On 25 Mar 2010, at 23:22:54, Steve Christensen wrote:
>
>> I'm curious why you need to know where the drag originated since it
>> generally shouldn't matter. Do you have to do some extra work in one case?
>> And wh
Is there any way to determine the source of a drag operation outside your own
application? For example, if I'm set to receive NSFilenamesPboardType, then I'd
like to distinguish between the Finder and Aperture as drag sources.
I had thought I'd seen a solution to this at one point, but can't see
I have a series of objects created periodically in my code which show no roots
under the GC Monitor in instruments, yet stubbornly refuse to be garbage
collected. I've tried forcing garbage collection and also clearing the stack in
various spots with objc_clear_stack(OBJC_CLEAR_RESIDENT_STACK).
dea what's happening here?
Jeffrey
On Nov 10, 2009, at 4:21 PM, Jeffrey J. Early wrote:
> After upgrading to 10.6.2 my Core Data model suddenly become incompatible
> with the stores it created on any previous system. Users that used my
> application under 10.5 or 10.6.1 or earlier, a
After upgrading to 10.6.2 my Core Data model suddenly become incompatible with
the stores it created on any previous system. Users that used my application
under 10.5 or 10.6.1 or earlier, are now presented with
"The model configuration used to open the store is incompatible with
the one
I have a multithreaded application with several NSOperationQueues and
it appears as if under heavy load conditions I'm overwhelming the
garbage collector so-to-speak.
I essentially have three queues which can be processing different
types of operations simultaneously.
- If I load up *one*
The dots show in the cell's "highlighted" state. If you send,
[cell setHighlighted: YES];
then you'll get dots... until it gets clicked on, then it
automatically un-highlights itself.
The solution is thus to subclass NSLevelIndicatorCell and override
isHighlighted to always return YE
broken by) IKImageBrowserView.
Hope that helps someone else,
Jeffrey
On Dec 28, 2008, at 11:02 PM, Jeffrey J. Early wrote:
I have had a number of troubles with IKImageBrowserView not
respecting other views trying to draw over the top of it. I have
worked around some of the issues, but this late
On Dec 30, 2008, at 2:39 PM, Benjamin Dobson wrote:
On 30 Dec 2008, at 12:52:45, Benjámin Salánki wrote:
Hi all,
I was playing around with core animation and was wondering if
sending animator to a view, specifically an NSImageView, will it
only manage animation of bounds and size and rot
I have had a number of troubles with IKImageBrowserView not respecting
other views trying to draw over the top of it. I have worked around
some of the issues, but this latest I can't seem to resolve.
I am trying to "dim" several of the views in my window by simply
placing a translucent view
17 matches
Mail list logo