Re: NSUserInterfaceItemIdentification -identifier vs -tag

2013-10-09 Thread jonat...@mugginsoft.com
On 9 Oct 2013, at 05:32, Keary Suska wrote: > On Oct 8, 2013, at 3:25 PM, Lee Ann Rucker wrote: > >> >> On Oct 8, 2013, at 1:59 PM, jonat...@mugginsoft.com wrote: >>> -tag and -identifier both have the advantage of being accessible from >>> within IB. >>> >>> J >> >> Any simple

Re: NSUserInterfaceItemIdentification -identifier vs -tag

2013-10-09 Thread dangerwillrobinsondanger
I lean toward tags as you can keep the speed of switch-case statements and use the macro NS_ENUM to define them out as human readable in code and to get code completion. String comparisons would be slightly slower. I think of the identifier as being more useful in caveman debugging. Sent fr

Re: Infinite Scroll View?

2013-10-09 Thread Dave
Hi, Got it working! The problem was partly due to tiredness and partly due to a misunderstanding about when layoutSubviews gets called. If you look at the Street Scroller sample, you'll see that it has its content "in-built", in fact it generate new content on the fly. The problem I had was th

Keeping Scroll Views in Sync

2013-10-09 Thread Dave
Hi, I've got a number of scroll views (A, B and C) I'm trying to keep in sync with each other, e.g. if the user scrolls A then I want B and C to scroll in sync with it. I've got this working by adding code in the scrollViewDidScroll method that passes the contentOffset onto the other two scroll

Re: Keeping Scroll Views in Sync

2013-10-09 Thread Tamas Nagy
Hi, in one of my apps I'm doing this too, but without any problems. I'm using scrollToPoint: method instead. [[NSNotificationCenter defaultCenter] addObserver:self selector:@selector(viewScrolled:)

Re: Keeping Scroll Views in Sync

2013-10-09 Thread Damian Carrillo
Dave, Try the following: - (void) scrollViewDidScroll:(LTWScrollView*) theScrollView { if (theScrollView.tag == kScrollViewA) { [self.scrollViewB setContentOffset:theScrollView.contentOffset animated:NO]; [self.scrollViewC setContentOffset:theScrollView.contentOffset an

Cocoaheads 92630 tonight, Wed. Oct 9 at 7pm

2013-10-09 Thread Scott Ellsworth
CocoaHeads Lake Forest will be meeting on the second Wednesday of the month. We will be meeting at the Orange County Public Library (El Toro) community room, 24672 Raymond Way, Lake Forest, CA 92630. We will be talking about Peter's ISO 8601 Date Formatter, recently updated, and appledoc, which g

Re: Responder chain query

2013-10-09 Thread Seth Willits
On Oct 8, 2013, at 12:33 PM, jonat...@mugginsoft.com wrote: >> Yup. Been doing it for years. There was some code written by Cathy Shive and >> Jonathan Dann to help with that called XSViewController. Don't know where >> the original source is now, but basically it managed a tree of view >> cont

Re: Keeping Scroll Views in Sync

2013-10-09 Thread Dave
Hi, I should have said, this is for iOS and it doesn't look like UIScrollView has the scrollToPoint method defined. There is also something about using notifications for this in a Mac Reference: https://developer.apple.com/library/mac/documentation/Cocoa/Conceptual/NSScrollViewGuide/Articles/Sy

Re: Keeping Scroll Views in Sync

2013-10-09 Thread Dave
Hi, This works really well, but of course there is no inertia/deceleration which feels a bit strange and I'm willing to bet marketing won't like it! I'm still playing about trying to get it to work. When you couple this with the Infinite Scroll View I've been working on, you get some very inter

NSDocument read from file, force save to different file

2013-10-09 Thread Trygve Inda
Version 1 of my app only saved it's (single container) data in ~/Library/Application Support/ Version 2 is document-based. I need to be able to load the data from the old App Support location (which is in a different format as well). This part is easy with a case within my readFromFileWrapper. On

Re: NSDocument read from file, force save to different file

2013-10-09 Thread Kyle Sluder
On Wed, Oct 9, 2013, at 08:22 PM, Trygve Inda wrote: > How can I do this? NSDocument *untitledDoc = [[NSDocumentController sharedDocumentController] makeDocumentForURL:nil withContentsOfURL:oldDocURL ofType:myUTI error:&err]; if (untitledDoc) { [untitledDoc makeWindowControllers]; [untitledDoc

Crash in datasource method when closing document

2013-10-09 Thread Shane Stanley
I have a document-based app, and it saves as a package. The document's window contains an outline view, where the user can drag items from the Finder or create new folders, and these will be saved to the package. I'm creating file wrappers of the items, stored in a property of the document. That

Re: Crash in datasource method when closing document

2013-10-09 Thread Kyle Sluder
> On Oct 9, 2013, at 10:06 PM, Shane Stanley wrote: > > The problem I'm having is that if I open a file, then add an item, say a > folder, then click the close button and choose Revert Changes, I (nearly > always) get an exception thrown on the outline view's datasource method > -outlineView:o

Re: Crash in datasource method when closing document

2013-10-09 Thread Jerry Krinock
On 2013 Oct 09, at 22:06, Shane Stanley wrote: > click the close button and choose Revert Changes, I (nearly always) get an > exception thrown on the outline view's datasource method > -outlineView:objectValueForTableColumn:byItem: Issues like this often crop up as soon as you try to make an

Re: Crash in datasource method when closing document

2013-10-09 Thread Shane Stanley
On 10 Oct 2013, at 5:09 PM, Kyle Sluder wrote: > A great place to start would be to actually look at and post what the > exception says… Yep. EXC_BAD_ACCESS (code=EXC_I386_GPFLT). It's happening on: - (id)outlineView:(NSOutlineView *)outlineView objectValueForTableColumn:(NSTableColumn *)tabl

Re: Crash in datasource method when closing document

2013-10-09 Thread Shane Stanley
On 10 Oct 2013, at 5:10 PM, Jerry Krinock wrote: > Issues like this often crop up as soon as you try to make an app which his > more complicated than Apple Sample Code :)) Yep. The curious thing is I've been working on this for some time, and it's only just cropped up. Now it might be that I

Re: Crash in datasource method when closing document

2013-10-09 Thread Jerry Krinock
On 2013 Oct 09, at 23:33, Shane Stanley wrote: > One of the first things I tried was putting a breakpoint on -windowWillClose: > The thing is, it doesn't get that far -- the breakpoint is never hit. In order to receive -windowWillClose:, the object implementing it must be the delegate of the

Re: Crash in datasource method when closing document

2013-10-09 Thread Shane Stanley
On 10 Oct 2013, at 5:39 PM, Jerry Krinock wrote: > In order to receive -windowWillClose:, the object implementing it must be the > delegate of the window which is closing. Yes, I already had -windowWillClose: implemented in my window controller (and -windowShouldClose:), and it gets called fi