Re: Deselect keyboard focus of an NSMatrix cell

hitting Return. In the bugreport I attached the project folder as demo. Cheers and thanks a lot, Jochen Moeller Am 25.07.2010 um 02:20 schrieb Kyle Sluder: On Jul 24, 2010, at 3:03 PM, Jochen Moeller jo.moel...@online.de wrote: Hi, so it is programmatically still not possible to give

Re: Deselect keyboard focus of an NSMatrix cell

, Jochen Moeller ___ 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: http

Deselect keyboard focus of an NSMatrix cell

display ]; // the focus ring remains [ window makeFirstResponder:[ window contentView ]]; // did not work. // Also [ window makeFirstResponder:anotherTextField ]; did not work. The key focus still remains in the textfield cell of the matrix. Any ideas? Thanks, Jochen Moeller

Re: Deselect keyboard focus of an NSMatrix cell

the NSMatrix but doesn't. Am 22.07.2010 um 22:26 schrieb Kyle Sluder: Jochen Moeller wrote: The -makeFirstResponder: method seems not to respond. -makeFirstResponder: returns a BOOL. See the documentation for -[NSWindow endEditingFor:] for what to do when -makeFirstResponder: returns

Interference of a variable name with Interface Builder

Hello List, Normally variable names don't interfere with method names. So I can write: CGFloat alphaValue = [ myCustomView alphaValue ]; Now, in an app the -drawRect: method of my custom view was not called although it should. I found out that the culprit was an outlet named alphaValue which

Re: Interference of a variable name with Interface Builder

Am 12.06.2010 um 23:22 schrieb Kyle Sluder: On Sat, Jun 12, 2010 at 2:11 PM, Jochen Moeller jo.moel...@online.de wrote: Normally variable names don't interfere with method names. Strictly speaking, Variable names can never interfere with method names. The compiler determines the type

NSSortDescriptor and Block

: But -sortedArrayUsingDescriptors: with a comparator results in Error: -[NSCFNumber rx]: unrecognized selector. So the method expects the key rx not in my class as it should but in the NSNumber class. A bug? Or is something wrong in my approach? Thanks for comments, Jochen Moeller Here

Re: NSSortDescriptor and Block

claims. The syntax of that method is a bit confusing. When using a selector the key is required, and when using a comparator it is not. Thanks again, Jochen Moeller Am 24.03.2010 um 11:12 schrieb Ben Trumbull: while experimenting with sorting methods I got a strange error message

Crash when MyDocument becomes the delegate of NSApplication

to process(gdb) So the MyDocument class seems to be overreleased by NSApplication. Is that a known issue? Never use an NSDocument subclass for delegates? Thanks for comments, Jochen Moeller ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do

Re: Crash when MyDocument becomes the delegate of NSApplication

Hi Kyle, You are right, I did not consider that. Because NSDocument is a controller object I used it similar to a self- made AppController. Thanks for your explanation. Jochen Moeller Am 25.07.2009 um 03:26 schrieb Kyle Sluder: Why would your document be an NSApplication delegate? What

Re: NSBezierPath problems, seems to be two bugs [solved]

() not erase that shadow? But the main problem is solved when no shadow is created in the overlay window. Greetings, Jochen Moeller Am 15.10.2008 um 13:56 schrieb Jochen Moeller: in the sample code Movie_Overlay (here with Xcode 3.1.1) http://developer.apple.com/samplecode/Movie_Overlay/index.html

NSBezierPath problems, seems to be two bugs

() ? Regards Jochen Moeller ___ 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

Re: NSBezierPath problems, seems to be two bugs

to try -fillRect: ;-) So one issue is solved, maybe the other will follow? Thanks again, Jochen Moeller On 15.10.2008, at 19:21, Aki Inoue wrote: Jochen, The behavioral differences you're observing is the result of NSCompositingOperation setting. NSRectFill() uses NSCompositeCopy

Re: NSObjectController needless in Intro to Bindings?

my question - Why is a second intervening NSController in form of an NSObjectController useful? Thanks again, Jochen Am 04.06.2008 um 03:59 schrieb Ken Thomases: On Jun 3, 2008, at 6:25 PM, Jochen Moeller wrote: Both versions run identical, so my question: Are both approaches equivalent

Re: NSObjectController needless in Intro to Bindings?

Thanks a lot for your explanation :-) Cheers, Jochen Am 04.06.2008 um 11:21 schrieb Ken Thomases: On Jun 4, 2008, at 3:18 AM, Jochen Moeller wrote: I already read this link and thought that the NSArrayController Mailbox represents this intervening NSController between the model object

NSObjectController needless in Intro to Bindings?

Jochen Moeller ___ 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: http