Re: Field editor in view-based table

Kyle, >> 1) to get the field editor to show I have to single click the text field >> and wait about 1s. > > Do you have a double-click action specified for the table view? If so, > NSTableView needs to wait to determine whether to send the click to the > hit view. Nope. > >> 2) The field ed

Re: Unwind segues

On Tue, 30 Apr 2013 13:13:47 -0700, Rick Mann said: >Where are these documented? Here! http://www.apeth.com/iOSBook/ch19.html#_unwind_segues :) m. -- matt neuburg, phd = m...@tidbits.com, A fool + a tool + an autorelease pool = cool! Programming iOS 6! http://shop

Re: Overlapping sibling views

On Apr 30, 2013, at 18:37 , Gideon King wrote: > How did you test it? Did you sort the views at all, or just leave them in the > order they were instantiated? My hierarchy is very simple. The content view contains a single view (which layer-backed in order to use a background color), and that

Re: Overlapping sibling views

How did you test it? Did you sort the views at all, or just leave them in the order they were instantiated? Did you try Sean's workaround? Regards Gideon On 01/05/2013, at 4:39 AM, Quincey Morris wrote: > > Nope. I just tried it again, setting the layer-backed checkboxes all the way >

Re: Unwind segues

OK. Here's an idea. Try a simple case. Create an empty app with a nav controller and a button to segue to another screen. Then one more to do the same. Set up a simple case where your method should get triggered on an exit case and see if it does in a simple, easily trashable file that yo

Re: Unwind segues

Oh! I think I found the problem. Looks like I might have to implement - (BOOL)canPerformUnwindSegueAction:(SEL)action fromViewController:(UIViewController *)fromViewController withSender:(id)sender which seems rather lame; the default behavior to return YES would be helpful. On Apr 30, 2013, at

Re: Unwind segues

On Apr 30, 2013, at 14:21 , Alex Zavatone wrote: > Odd. I've never played around with the exits yet. If you hook it up to a > UIButton and trigger is manually with a tap, does it get called? Yes, that's how I had it before. I just wanted to try the "new" way. > Try that and set a breakpoin

Re: Unwind segues

Odd. I've never played around with the exits yet. If you hook it up to a UIButton and trigger is manually with a tap, does it get called? Try that and set a breakpoint on it and see if there is a clear call chain. If it doesn't appear in the execution chain, then it might be one of those har

Re: Unwind segues

On Apr 30, 2013, at 14:15 , Alex Zavatone wrote: > Are you expecting these to be called when a segue unwinds because I can. Of > see these declared in any of the docs. If something calls an IBAction, these > are generally attached to an IBOutlet (a button) and are triggered on > touchUpInsid

Re: Unwind segues

Are you expecting these to be called when a segue unwinds because I can. Of see these declared in any of the docs. If something calls an IBAction, these are generally attached to an IBOutlet (a button) and are triggered on touchUpInside, so they need to be wired up to the button. I hope I am u

Re: Unwind segues

On Apr 30, 2013, at 13:56 , Alex Zavatone wrote: > Looks Iike the closest I can find is within the UIViewController. I searched > all the frameworks of iOS 6.0 using Dash and Xcode 4.6.1. > > If it is an IBOutlet, then this is your method. You need to create it. Hey, Alex, thanks. I'm not su

Re: Unwind segues

Looks Iike the closest I can find is within the UIViewController. I searched all the frameworks of iOS 6.0 using Dash and Xcode 4.6.1. If it is an IBOutlet, then this is your method. You need to create it. Sent from my iPad On Apr 30, 2013, at 4:13 PM, Rick Mann wrote: > Where are these docu

Unwind segues

Where are these documented? I found some information on Stackoverflow. I put an -unwind: method in the same controller as the one that contains the button that's connected to the exit. IB allows me to connect to this unwind: method, but it never calls it at run time. I tried putting a method in

Re: NSTextField binding returns nil not empty string

On Apr 30, 2013, at 1:14 PM, Chris Paveglio wrote: > What is the best way to handle this? I have a table view (using cell views) > which has multiple text fields in it. I have an arrayController that holds an > array of the custom objects that hold the data for each tableCellView (row). > The a

Strange tracking rect problem

Our doc windows get a tracking rect (actually, our main view does) for setting the cursor: [[NSTrackingArea alloc] initWithRect:localBox options:(NSTrackingInVisibleRect | NSTrackingCursorUpdate | NSTrackingMouseMoved | NSTrackingMouseEnteredAndExited | NSTrackingActiveInKeyWindow) owner:self

NSTextField binding returns nil not empty string

What is the best way to handle this? I have a table view (using cell views) which has multiple text fields in it. I have an arrayController that holds an array of the custom objects that hold the data for each tableCellView (row). The array is made in the appDelegate and it always consists of te

Re: Overlapping sibling views

On Apr 30, 2013, at 08:55 , Mike Abdullah wrote: > On 30 Apr 2013, at 16:53, Gideon King wrote: > >> So it sounds as if as long as I have all my views in the entire hierarchy >> layer backed, my sibling views should always draw in order. > > Yup. Bear in mind WebViews don't support being lay

Re: Laying out text in NSTextView around a subview

On Apr 30, 2013, at 7:01 AM, Jason Brennan wrote: > Yeah what I'm trying to do mostly is a "block" element in the text, "inline" > is just a side thing, not essential. What I'm trying to do is best described > as an analogy with HTML. > > Let's say I've got the following HTML: > > This is a pa

Re: Overlapping sibling views

On Tue, 30 Apr 2013 01:30:00 -0700, Quincey Morris said: >On Apr 30, 2013, at 00:39 , Gideon King wrote: > >> My scenario is a whole lot of sibling, potentially translucent, >overlapping, layer backed views. > >I've never seen any evidence that sibling *NSView*s draw in the wrong >order since 10.

NSOutlineView Storing/Restoring Disclosure Paths

We have a hierarchy, displayed in an NSOutlineView. We also allow the user to specify the root at any of the top two levels. When moving the root down the tree, if there is no selection, the new root is the first element of the top-level tree. If rows are selected, we use the first index path to

Re: Overlapping sibling views

On 30 Apr 2013, at 16:53, Gideon King wrote: > So it sounds as if as long as I have all my views in the entire hierarchy > layer backed, my sibling views should always draw in order. Yup. Bear in mind WebViews don't support being layer-backed (still!), which can throw a spanner in the works.

Re: Overlapping sibling views

So it sounds as if as long as I have all my views in the entire hierarchy layer backed, my sibling views should always draw in order. This makes me happy :) … and the documentation wrong :( - I'll report that. Regards Gideon ___ Cocoa-dev maili

Animate magnifyToFitRect:

Hi, in my custom NSClipView class I would like to subclass the method smartMagnifyWithEvent and zoom the rect on which the user has double tapped. So I properly detect the rect to magnify, then I tell the scrollView to [self.superview magnifyToFitRect:boxFrame]; and I properly get the view zoom

Re: Laying out text in NSTextView around a subview

Yeah what I'm trying to do mostly is a "block" element in the text, "inline" is just a side thing, not essential. What I'm trying to do is best described as an analogy with HTML. Let's say I've got the following HTML: This is a paragraph Another paragraph I'm only using as an example because i

Re: Overlapping sibling views

On Tuesday, 30. April 2013 at 10:42, Mike Abdullah wrote: > Layer-backed views always *appear* above non-layer-backed views. Effectively, > all non-layer-backed views get rendered into a single layer that makes up the > entire window. Thanks, didn't know this. Never needed layer backed view unti

Re: Overlapping sibling views

On 30 Apr 2013, at 09:38, Robert Vojta wrote: >> I've never seen any evidence that sibling *NSView*s draw in the wrong order >> since 10.5. I believe that 'drawRect:' is correctly called in the >> back-to-front order of the sibling arrangement in the parent view. >> >> However, I *have* seen

Re: Overlapping sibling views

> I've never seen any evidence that sibling *NSView*s draw in the wrong order > since 10.5. I believe that 'drawRect:' is correctly called in the > back-to-front order of the sibling arrangement in the parent view. > > However, I *have* seen firsthand, in the last few weeks, that the layers of

Re: Overlapping sibling views

On Apr 30, 2013, at 00:39 , Gideon King wrote: > My scenario is a whole lot of sibling, potentially translucent, overlapping, > layer backed views. I've never seen any evidence that sibling *NSView*s draw in the wrong order since 10.5. I believe that 'drawRect:' is correctly called in the back

Re: Overlapping sibling views

The docs are out of date. Overlapping views work properly as of 10.5 (albeit you might run into performance problems if you push it too far). Please use the feedback thing on the bottom of the docs to let Apple know it's wrong! On 30 Apr 2013, at 08:39, Gideon King wrote: > Hi, I had to design

Overlapping sibling views

Hi, I had to design my whole view system to work around the problems with overlapping sibling views not being guaranteed to be drawn in a specific order, but today I came across some posts that suggested that this was no longer the case. In the current 10.8 documentation it still says: "Note: F