Open Recent Crash

Whenever I do in TextEdit: File → Open Recent I get a crash. Obviously the list of recent documents is somehow corrupted. So I renamed "~/Library/Preferences/com.apple.TextEdit.LSSharedFileList.plist" to: "LSSharedFileList bad.plist", started TextEdit and got the same crash. Also got a new "LSSh

Re: Open Recent Crash

Whenever you do something with defaults, ignore the plist file. Instead always use the command line tool defaults. There have been major changes throughout the system releases as to how the defauls daemon works ___m i c h a e l s t a r k e geschäftsführer HicknHack Software GmbH www.hickn

Added Toolbar, now main window can't be resized

Everyone, I got my app working pretty much as I desired, then came up with a reason to add a Toolbar. I opened my NIB in IB and dragged one over, added the needed buttons easily, then connected them up so my app responds to them. The only thing is, since adding the Toolbar, my main window has

Re: wits end with nsview and nsrectfill()

Hi After trying out everything, I finally found how to remove that difference in background color. I couldn’t find any rationale in this patch effect, so I turned the outline selection highlight to none (regular, i.e. plain white also works). So if you take a view-based outline view (or maybe ta

WTF is happening?

This got me scratching my head, hard. Why would class_respondsToSelector() crash? (BTW this is used in a class search loop so I cannot use [NSObject respondsToSelector:] just yet.) /Users/technix/Developer/Subtitler Pro/Frameworks/SubtitleKit/SubtitleKitTests/SKSubripParseTest.m:33: error: -[S

Re: wits end with nsview and nsrectfill()

> On Dec 13, 2014, at 10:20 AM, Navneet Kumar wrote: > > So if you take a view-based outline view (or maybe table view as well) and > fill a table column’s view’s background with NSRectFill() or any other and > add as sub view a transparent text field, upon refresh the text field and the > re

Re: WTF is happening?

Why do you think the problem is with “respondsToSelector:”? The error says you’re accessing past the end of a string. On Dec 13, 2014, at 10:20 AM, Maxthon Chan wrote: > This got me scratching my head, hard. Why would class_respondsToSelector() > crash? (BTW this is used in a class search loo

Re: WTF is happening?

On Sat, Dec 13, 2014, at 10:19 AM, Phillip Mills wrote: > Why do you think the problem is with “respondsToSelector:”? The error > says you’re accessing past the end of a string. Because the crash happens in a call stack that originates in class_respondsToSelector, and involves none of Maxthon's c

Re: WTF is happening?

What I am doing here is scanning all loaded classes for subclasses of a certain class. Before any NSObject method can be issued I have to check if it is actually NSObject or NSProxy derivative instead of an Object derivative that does not support NSObject methods. This calls for runtime equivale

Re: WTF is happening?

If all you care about is if an object is a proxy or not, look at isProxy. -- Gary L. Wade (Sent from my iPad) http://www.garywade.com/ > On Dec 13, 2014, at 11:06 AM, Maxthon Chan wrote: > > What I am doing here is scanning all loaded classes for subclasses of a > certain class. Before any NSOb

Re: WTF is happening?

Ain’t work! Will crash if an Object derivative showed up. I am scanning ALL loaded classes and only subclasses of a certain class is interested. But due to the nature of this class scanning before I can make sure that the class derives from NSObject I cannot call any method on it. > On Dec 14,

Re: WTF is happening?

Are you saying that Apple's well-documented approach to see if an object is derived from NSProxy does not work? If that's the case, you need to submit a bug report to Apple. That's a serious issue that only Apple can help you with. If you are using objects not derived from NSObject nor NSProxy,

Re: WTF is happening?

NSProxy checking actually work, but throwing those classes that derive from Object class (note I used capitalised O here, the old Object class from early NeXT times, also used heavily in OS X kernel, GCD and Mach ports) into the mix means that no method can be sent before class is determined. I

Re: wits end with nsview and nsrectfill()

On 13 Dec 2014, at 16:45, Bill Cheeseman wrote: >> On Dec 13, 2014, at 10:20 AM, Navneet Kumar wrote: >> >> So if you take a view-based outline view (or maybe table view as well) and >> fill a table column’s view’s background with NSRectFill() or any other and >> add as sub view a transparent

Re: wits end with nsview and nsrectfill()

> On Dec 13, 2014, at 3:08 PM, Uli Kusterer > wrote: > >> I believe the "Source List" setting means that an NSVisualEffectView lies >> behind the text field. The only documentation I have been able to find about >> NSVisualEffectView is (1) in the AppKit release note for Yosemite (which >>

Re: wits end with nsview and nsrectfill()

> On 14 Dec 2014, at 2:20 am, Navneet Kumar wrote: > > So if you take a view-based outline view (or maybe table view as well) and > fill a table column’s view’s background with NSRectFill() or any other and > add as sub view a transparent text field, upon refresh the text field and the > rest

Re: WTF is happening?

The Object class is not used anywhere is OS X. It is deprecated and should have been removed from the runtime long time ago. The OS X kernel does not even include obj runtime, so it can’t possibly use the Object class. Mach port are integer that represent kernel object and not classes. The ro

Re: WTF is happening?

I called objc_copyClassList() to get all loaded classes so that I can scan all loaded classes for decedents of a certain class, and Object is part of this. I am using this as the basis of a plugin mechanism, once the plugin bundle is loaded it should be detected by the app itself, and the app sh