Thoughts on a line-at-a-time data-reading class

I'm thinking of creating a Document-based app for my pet project. And I'm thinking about how to read the data in. I could load all the data, change it to a string, then process it; but I want to process the data in layers and do some work before string conversion. Specifically, I want to

Setting the Null Placeholder for bindings

I have a TextField bound to Shared User Defaults Controller. The Null Placeholder is set to “default”. When the window comes up, it shows the value from NSUserDefaults registerDefaults:. Ok When I remove the string from the TextField, I see a grey value “default”. Also to be expected. The

Re: Apple Bug no response

> You might get an automated email when a future build is available asking you > to re-test. You may get a note that your bug is a duplicate. You may never > get a response at all. Or… …yesterday I got feedback asking if a bug I reported in an early *Yosemite* seed was resolved in the latest

Re: Storyboard weakness

I really wanted to be able to take advantage of the storyboard editor for many reasons. Turns out, you can (thanks to Daniel Stenmark for cluing me in). You just can't drop in a UICollectionViewController (this is a lame weakness). But you can put in a UIViewController, and drop in a

Re: Storyboard weakness

Would it help if you created an XIB tor that particular scene? If you delete your top level view for that scene in the storyboard, but that scene is wired to your view controller, your view controller will load that XIB for the top level view. That XIB also has to be wired to your view

Can't generate receipt OS X after 173 exit

I am no longer able to generate a receipt after exiting with code 173. When I launch, I get a box saying that the app was purchased on another computer and that I need to validate it. I enter my Apple ID and password, but I get "An unexpected error occurred while signing in" The Apple ID could

Re: Storyboard weakness

> On Mar 9, 2016, at 18:09 , Daniel Stenmark wrote: > > If you’re still having issues, feel free to post up and send us a GitHub link > to a sample project exhibiting this behavior. Setting up a UICollectionView > fairly straight-forward; something’s being overlooked

Re: Storyboard weakness

If you’re still having issues, feel free to post up and send us a GitHub link to a sample project exhibiting this behavior. Setting up a UICollectionView fairly straight-forward; something’s being overlooked here. Dan > On Mar 9, 2016, at 5:55 PM, Daniel Stenmark

Re: Storyboard weakness

Did you set the prototype cell’s Reusability Identifier? http://i.imgur.com/1uLxYPo.png Dan On Mar 9, 2016, at 5:29 PM, Rick Mann > wrote: On Mar 9, 2016, at 16:05 , Daniel Stenmark >

Re: Storyboard weakness

I did. This is at least the second bug about this I've reported. Basically, every few years I end up having to do this, and work around the problem one way or another. I usually write a bug report when I do. It seems Apple has improved things slightly (e.g., you can actually still build cells

Re: Storyboard weakness

Write a bug like I did saying how difficult it is using Interface Builder to construct the UI you desire. Give as concrete an example as you can, and if you've seen an Apple app do similar, mention it. If you've seen a third party app do it, mention it, too. Sometimes you'll get some free tech

Re: Storyboard weakness

> On Mar 9, 2016, at 16:05 , Daniel Stenmark wrote: > >> Because I want all the benefits the specific view controller gives me, >> namely the ability to build the cells right in the view. > > What’re you talking about? You can still build custom UICollectionView

Re: Storyboard weakness

> On Mar 9, 2016, at 17:13 , Gary L. Wade wrote: > > If you can require iOS 9, pinning appears to be supported. If earlier, you > might be able to do what you want by overriding a layout class. I haven't > tried it myself, though. I know your pain with respect to

Re: Storyboard weakness

If you can require iOS 9, pinning appears to be supported. If earlier, you might be able to do what you want by overriding a layout class. I haven't tried it myself, though. I know your pain with respect to a UITabBarController, though, but that was easy to re-enclose in another view, although

Re: Storyboard weakness

> On Mar 9, 2016, at 17:05 , Gary L. Wade wrote: > > I'm not sure exactly about your layout, but maybe what you want are > supplementary views? Supplementary views scroll with the content. I want non-scrolling views. > -- > Gary L. Wade (Sent from my iPhone) >

Re: Storyboard weakness

I'm not sure exactly about your layout, but maybe what you want are supplementary views? -- Gary L. Wade (Sent from my iPhone) http://www.garywade.com/ > On Mar 9, 2016, at 3:04 PM, Rick Mann wrote: > > There's a severe weakness in Storyboards for which I'm hoping a

Re: Storyboard weakness

> On Mar 9, 2016, at 16:05 , Daniel Stenmark wrote: > >> Because I want all the benefits the specific view controller gives me, >> namely the ability to build the cells right in the view. > > What’re you talking about? You can still build custom UICollectionView

Re: Safe cross references between scenes in an OS X storyboard

On Mar 9, 2016, at 16:22 , Quincey Morris wrote: > >> NSWindowController Sorry, my brain was stuck on window controllers, but you’re doing this in the view controller. Same code, really. ___ Cocoa-dev mailing

Re: Safe cross references between scenes in an OS X storyboard

On Mar 9, 2016, at 13:31 , Bill Cheeseman wrote: > >static var controller: MainContentViewController? { >get { >return MainContentViewController.controller >} >set(newController) { >MainContentViewController.controller =

Re: Apple Bug no response

> On Mar 9, 2016, at 6:52 PM, Michael David Crawford > wrote: > > I have a bug in Apple's sample code that would be a trivial fix, that > has been open for eight years. > > By contrast I've reported a few kernel bugs. Each was fixed in the > very next build. My

Re: Storyboard weakness

> On Mar 9, 2016, at 16:05 , Daniel Stenmark wrote: > >> Because I want all the benefits the specific view controller gives me, >> namely the ability to build the cells right in the view. > > What’re you talking about? You can still build custom UICollectionView

Re: Storyboard weakness

> Because I want all the benefits the specific view controller gives me, namely > the ability to build the cells right in the view. What’re you talking about? You can still build custom UICollectionView cells right into the view when using a plain old UIViewController. Dan

Re: Storyboard weakness

Because I want all the benefits the specific view controller gives me, namely the ability to build the cells right in the view. I guess I have to give up on that. One small silver lining is I can break those into NIBs and not duplicate them (I have three different collection views that all

Re: Apple Bug no response

I have a bug in Apple's sample code that would be a trivial fix, that has been open for eight years. By contrast I've reported a few kernel bugs. Each was fixed in the very next build. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do

Re: Storyboard weakness

Why are you locking yourself into a heavily customized UICollectionViewController? Why not just use a generic UIViewController and hook up your view elements the old fashioned way? Dan > On Mar 9, 2016, at 3:04 PM, Rick Mann wrote: > > There's a severe weakness in

Re: Storyboard weakness

I might be misunderstanding, but why not just use a regular UIViewController scene, throw a collection view in it, throw your other view into it too, and then conform to UICollectionViewDataSource and -Delegate “manually”? It’s a few more outlets to connect by hand but isn’t

Re: Apple Bug no response

> On Mar 9, 2016, at 1:32 PM, Trygve Inda wrote: > > I have an open bug report > > How long should I expect to wait for a response? My experience with issues. If you have a graphics related bug (OpenGL, Core Animation, Graphics Adapter Specific) they get on it

Storyboard weakness

There's a severe weakness in Storyboards for which I'm hoping a better solution exists. When you create a scene for say, a UICollectionView, the Storyboard makes it very easy, but it also imposes a severe limitation. In my case, my UICollectionViewController subclass lives inside a

Re: Safe cross references between scenes in an OS X storyboard

> On Mar 9, 2016, at 1:00 PM, Quincey Morris > wrote: > > What you can do instead is subclass NSWindowController, and use > ‘windowDidLoad’ as your opportunity to save your own strong reference to the > WC. (In Swift, I think I’d make it a static property

Re: Safe cross references between scenes in an OS X storyboard

On Mar 9, 2016, at 11:36 , Bill Cheeseman wrote: > > But don't I still need to use optionals if I declare the window controller or > content view controller instance variable in AppDelegate but don't set it > until later in the window controller's windowDidLoad() method?

Re: Apple Bug no response

#4145901 .. June 12, 2005 > On Mar 9, 2016, at 4:02 PM, Gary L. Wade wrote: > > My oldest open bug will be 10 years old by WWDC 2016. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin

Re: Apple Bug no response

My oldest open bug will be 10 years old by WWDC 2016. -- Gary L. Wade (Sent from my iPhone) http://www.garywade.com/ > On Mar 9, 2016, at 12:50 PM, Eric E Dolecki wrote: > > I have bugs that have celebrated their fifth birthdays. Fire and forget. > > Sent from my iP6+ >

Re: Apple Bug no response

I have bugs that have celebrated their fifth birthdays. Fire and forget. Sent from my iP6+ > On Mar 9, 2016, at 3:44 PM, Hunter Hillegas wrote: > > You must be new here. ;-) > > You might get an automated email when a future build is available asking you > to

Re: Apple Bug no response

You must be new here. ;-) You might get an automated email when a future build is available asking you to re-test. You may get a note that your bug is a duplicate. You may never get a response at all. I have many open bugs from years back which usually either means the issue is still out

Re: Apple Bug no response

On Mar 9, 2016, at 2:32 PM, Trygve Inda wrote: > > I have an open bug report > > rdar://24316348 > > Apple asked for an example to reproduce which I sent on January 27, but I > have heard nothing since. This is a fairly simple bug (NSTextFields can't > fully justify

Apple Bug no response

I have an open bug report rdar://24316348 Apple asked for an example to reproduce which I sent on January 27, but I have heard nothing since. This is a fairly simple bug (NSTextFields can't fully justify on 10.11). How long should I expect to wait for a response? Thanks, Trygve

Re: Safe cross references between scenes in an OS X storyboard

> On Mar 9, 2016, at 1:00 PM, Quincey Morris > wrote: > > On Mar 9, 2016, at 05:59 , Bill Cheeseman wrote: >> >> But the main thrust of my question was whether this is a safe and sensible >> way to crossreference other storyboard

Re: Safe cross references between scenes in an OS X storyboard

On Mar 9, 2016, at 05:59 , Bill Cheeseman wrote: > > But the main thrust of my question was whether this is a safe and sensible > way to crossreference other storyboard scenes -- at least when > prepareForSegue(_:sender:) isn't available, as it isn't here. Having thought

Re: Safe cross references between scenes in an OS X storyboard

> On Mar 9, 2016, at 8:42 AM, Roland King > wrote: > > just > > return NSApp.mainWIndow?.contentViewController as? > MainContentViewController > > works without all the guard and intermediate variables and still returns the > same optional.

Re: UICollectionView Moving

Ok - I think this is the final question. I've created a layout that is essentially a bunch of ragged bottom columns - like a Trello or Kanban board. The items in the collection view are "stories" with size around 100x100. To begin with, I prepopulate the underlying datastore and things are great,

Re: Safe cross references between scenes in an OS X storyboard

> On 9 Mar 2016, at 21:32, Bill Cheeseman wrote: > > I am using storyboards in an OS X application written in Swift 2. It is a > single window "shoebox" application that does not use NSDocument or Core > Data. It is built with the Xcode 7.2.1 storyboard template, where

Safe cross references between scenes in an OS X storyboard

I am using storyboards in an OS X application written in Swift 2. It is a single window "shoebox" application that does not use NSDocument or Core Data. It is built with the Xcode 7.2.1 storyboard template, where the storyboard entry point is the main window controller scene and a "window