Really? This list has no opinions? That's hard to imagine :-)
--
Seth Willits
> On Aug 8, 2015, at 1:15 PM, Seth Willits wrote:
>
> Let's stipulate that _Nullable and _Nonnull are great to have because they
> can catch bugs and express API intent better than before, so we want them.
> The
Hi,
I have an existing iOS application which is supports from iOS 8. i want
to add new features only for iOS 9.
I have created a new storyboard for iOS 9(Main.storyboard) which is using
the iOS 9 features like UIStackView. Appropriate storyboard file is
instantiated based on the Device OS versi
On Aug 16, 2015, at 09:20 , Sasikumar JP wrote:
>
> But i am getting compilation error on Main.storyboard "UIStackView before
> iOS 9.0"
What’s the “Build for” setting in the File inspector for Main.storyboard? The
default is “deployment target”, which means iOS 8 in your case, but you’ll need
On Aug 16, 2015, at 09:10 , Seth Willits wrote:
>
> Really? This list has no opinions? That's hard to imagine :-)
Well, I do, but I didn’t post it because I didn’t think you’d like it.
I don’t think it’s worth annotating private methods at all (in general — I’m
sure there are specific cases wh
Quincey,
Thank you for the information. I changed the build for value to iOS 9.
it works fine now. I am able to run the application on both iOS 9 and iOS 8.
Regards
Sasikumar JP
On Sun, Aug 16, 2015 at 10:24 PM, Quincey Morris <
quinceymor...@rivergatesoftware.com> wrote:
> On Aug 16, 2015,
I’ve annotated the public methods of the API of a framework and though I
haven’t yet I will annotate internal methods and functions as well.
I found a small number of issues where my thinking had not been clear, and that
having to stop and consider what was intended when annotating the public AP
On Wed, 12 Aug 2015 15:50:35 -0600, Alex Kac said:
>I have an OS X app signed with Developer ID. It is NOT sandboxed (I
>suppose I could, but I'd prefer to stay away from that for a bit
>longer).
>
>I need my helper and main app to share prefs. There must be a simple
>way to do this for now. I kno
I'm currently writing a storyboard inspector for helping to create more modular
app pieces in iOS (8)
The idea is if you have enough functionality that is self contained enough, it
should (I hope) be organizationally more efficient to create a storyboard that
handles the desired functionality a
On Aug 16, 2015, at 3:09 PM, Alex Zavatone wrote:
> So, I look at UIStoryboard.h and the docs and see that there are 3 methods.
> No properties.
> And in using it, I find out that in addition to the 3 methods within
> UIStoryboard.h, inside a an instance of UIStoryboard, there are a bunch of
On Aug 16, 2015, at 4:49 PM, Ken Thomases wrote:
> On Aug 16, 2015, at 3:09 PM, Alex Zavatone wrote:
>
>> So, I look at UIStoryboard.h and the docs and see that there are 3 methods.
>> No properties.
>
>> And in using it, I find out that in addition to the 3 methods within
>> UIStoryboard.h
> On 16 Aug 2015, at 22:18, Alex Zavatone wrote:
>
>
> On Aug 16, 2015, at 4:49 PM, Ken Thomases wrote:
>
>> On Aug 16, 2015, at 3:09 PM, Alex Zavatone wrote:
>>
>>> So, I look at UIStoryboard.h and the docs and see that there are 3 methods.
>>> No properties.
>>
>>> And in using it, I fi
On Aug 16, 2015, at 4:18 PM, Alex Zavatone wrote:
> On Aug 16, 2015, at 4:49 PM, Ken Thomases wrote:
>
>> On Aug 16, 2015, at 3:09 PM, Alex Zavatone wrote:
>>
>>> Why isn't it in Apple's documentation for storyboards?
>>
>> Because these are private implementation details. They are subject t
On Aug 16, 2015, at 5:35 PM, Ken Thomases wrote:
> On Aug 16, 2015, at 4:18 PM, Alex Zavatone wrote:
>
>> On Aug 16, 2015, at 4:49 PM, Ken Thomases wrote:
>>
>>> On Aug 16, 2015, at 3:09 PM, Alex Zavatone wrote:
>>>
Why isn't it in Apple's documentation for storyboards?
>>>
>>> Because
>
> If the debugger's variable pane exposes it, it's misleading if it doesn't
> somehow indicate that it's not for the developer to access.
It is there for the developer to access -- when debugging. Might even be
useful. I sometimes find the information useful when trying to understand how
so
Hello.
I have a window controlled by a NSWindowController subclass with a standard
nsscrollview. (Outlets are connected).
I load a custom view via a NSViewController subclass. (view outlet is
connected).
The custom view is not visible.
@implementation AppDelegate
- (IBAction) newWindow:(id)send
15 matches
Mail list logo
