On Mar 9, 2016, at 18:47 , Trygve Inda wrote:
>
> 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”
Did you ever solve this? I was going
On Mar 10, 2016, at 17:05 , Eric Gorr wrote:
>
> I have a Core Data Document Based OS X application written in swift and using
> storyboards. Whenever I build and launch the app, instead of automatically
> opening the last opened document(s), it will create a new document. What I
> want to be
I have a Core Data Document Based OS X application written in swift and using
storyboards. Whenever I build and launch the app, instead of automatically
opening the last opened document(s), it will create a new document. What I want
to be able to do is have the application automatically restore
> On Mar 10, 2016, at 1:35 PM, Ken Thomases wrote:
>
> On Mar 10, 2016, at 3:21 PM, Doug Hill wrote:
>>
>> I can see that people use multiple constraints when moving between different
>> layouts. But what I don’t get is how there can be an alignment constraint
>> that doesn’t cause a layout u
On Mar 10, 2016, at 3:21 PM, Doug Hill wrote:
>
> I can see that people use multiple constraints when moving between different
> layouts. But what I don’t get is how there can be an alignment constraint
> that doesn’t cause a layout update when views move? How does autolayout
> decide to use t
Unfortunately, we have an iOS 8 requirement so we can’t use stack views.
I can see that people use multiple constraints when moving between different
layouts. But what I don’t get is how there can be an alignment constraint that
doesn’t cause a layout update when views move? How does autolayout
On Mar 10, 2016, at 12:59 , Doug Hill wrote:
>
> I set up an auto layout constraint so that an another view is a fixed number
> of pixels from the side view. I then want to move the origin of the side view
> and have the other view move with it.
>
> If I set up an alignment constraint so trail
I’m trying to implement a side panel that moves into place horizontally and
push content over when it is shown. I set up an auto layout constraint so that
an another view is a fixed number of pixels from the side view. I then want to
move the origin of the side view and have the other view move
> On Mar 9, 2016, at 11:53 PM, Daryle Walker wrote:
>
> In my head, I came up with (in Swift):
This is exactly the kind of thing that frustrates me about the Cocoa APIs:
they’re so very bad at streams and producer/consumer patterns. This kind of
problem really calls out for a proper stream A
> On Mar 9, 2016, at 7:22 PM, Quincey Morris
> wrote:
>
> No, it’s *really* a property, so like this:
>
>> class MainContentViewController: NSWindowController {
>>
>> static private(set) var controller: MainContentViewController! //
>> defaults to nil until set
>>
>> override
Dear List:
I am wondering how should I assemble a new toolchain, a new platform that it
can target and a new SDK for it to develop on? The new toolchain, platform and
SDK should be standalone.
Sent from my iPhone
smime.p7s
Description: S/MIME cryptographic signature
___
That was it. Thanks Luke!
Really digging this control ...
On Wed, Mar 9, 2016 at 10:36 AM, Luke Hiesterman wrote:
> UICollectionView doesn’t know that your layout is conceptually columns, so
> when a section is empty, it has no concept of what space is appropriate to
> drop items into an empty
12 matches
Mail list logo
