ubscription:
>> https://lists.apple.com/mailman/options/cocoa-dev/dave%40looktowindward.com
>>
>> This email sent to d...@looktowindward.com
>
> ___
>
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>
> Please d
eport.
It might not be small.
> Then file a bug report
> at https://bugreport.apple.com.
>
> --Kyle
>
>>
>> --Richard Charles
> ___
>
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>
> Please do not post adm
>
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
> https://lists
or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/cocoa-dev/dangerwillrobinsondanger%40gmail.com
>
> This email sent to dangerwillrobinsondan...@gmai
nent Manager is/was just an ancient
>>> DLL-loading mechanism. IIRC it was mostly used by QuickTime. What are you
>>> using the Component Manager for?
>>>
>>> ―Jens
>>>
>> ___
>>
>> Cocoa-de
not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/cocoa-dev/dangerwillrobinsondanger%40gmail.com
>
> This email se
All together, looks like NSWorkspace should enable doing this as long as you
don't hit some permissions restrictions on some folders.
Less code no doubt too.
Cool.
> On 1 Nov 2016, at 17:25, Ken Thomases wrote:
>
>> On Nov 1, 2016, at 3:20 AM, Gerriet M. Denkmann wrote:
>>
>> What I really
ist.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/cocoa-dev/dangerwillrobinsondanger%40gmail.com
>
> This email sent to dangerwillrobinsondan...@gmail.com
__
e.com)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/cocoa-dev/dan
s.apple.com)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/cocoa-dev/dangerwillrobinsondanger%40gmail.co
Subscription:
>> https://lists.apple.com/mailman/options/cocoa-dev/garywade%40desisoftsystems.com
>>
>> This email sent to garyw...@desisoftsystems.com
>
>
> ___
>
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>
; Gabriel.
>
>
> ___
>
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help
It's not Toll Free bridged.
And Fritz, you contribute so much to folks, nobody would blink if you missed
anything.
Sent from my iPhone
> On Sep 8, 2016, at 1:41 AM, Fritz Anderson wrote:
>
> “dangerwillrobinsondanger” correctly points to Core Foundation. I’m
> embarrassed
> On Sep 7, 2016, at 6:09 PM, Dave wrote:
>
> I’m already using Accessibility but the notification I get when a window is
> created is posted to too late for it to help in this case.
>
> I’m also using Event Taps, I want to be able to stop events being fired to
> the window until I have recei
moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/cocoa-dev/dangerwillrobinsondanger%40gmail.com
>
> This email sent to dangerwillrobinsondan...@gmail.com
__
ng list (Cocoa-dev@lists.apple.com)
>>>
>>> Please do not post admin requests or moderator comments to the list.
>>> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>>>
>>> Help/Unsubscribe/Update your Subscription:
>>> https://lists
;>>>>> Rick Mann
>>>>>> rm...@latencyzero.com
>>>>>>
>>>>>>
>>>>>>
>>>>>> ___
>>>>>>
>>>>>> Cocoa-
ntact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/cocoa-dev/dangerwillrobinsondanger%40gmail.com
>
> This email sent to dangerwillrobinsondan...@gmail.com
> On Aug 24, 2016, at 2:56 AM, Andreas Falkenhahn
> wrote:
>
> Is that your personal opinion or is this documented anywhere?
There's not anything to the contrary I've seen.
Look no further than LSUIElement.
There is an info plist key that says you have no UI, and guess what it works
even if
comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/cocoa-dev/dangerwillrobinsondanger%40gmail.com
>
> This email sent to dangerwillrobinsondan...@gmail.com
__
> On Aug 22, 2016, at 10:26 PM, Andreas Falkenhahn
> wrote:
>
> Does anybody have an idea
> what could cause this behaviour on 10.6 and how I can fix this?
http://bfy.tw/7Kcc
there is a great resource here.
___
Cocoa-dev mailing list (Cocoa-dev@lis
> On Aug 20, 2016, at 2:50 AM, Quincey Morris
> wrote:
>
> AFAICT, the main reason *not* to use ‘new’ is to avoid generating anxiety for
> those who come back to read the code later, and who might worry that the
> inconsistency means something.
Even though new has been a synonym for alloc]
> On Aug 12, 2016, at 11:20 AM, Steve Sisak wrote:
>
> Actually, to be pedantic, class cluster is an implementation detail ― was
> trying to impedance match to OP’s experience level.
>
> Was speaking purely in terms of public interfaces (since he’s a consumer
> rather than implementor)
Polit
> On Aug 12, 2016, at 9:16 AM, Steve Sisak wrote:
>
> There’s a standard idiom where immutable classes frequently have mutable
> subclasses (which expose the mutating methods).
>
> In this case, it’s common for the immutable (super)class to adopt NSCopying
> and the mutable subclass to also
se do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/cocoa-dev/dangerwillrobinsondanger%40gmail.com
>
> This email sent
>
>
> ___
>
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsub
Just be sure to write tests that prove it does what you want it to do. ;)
Sent from my iPhone
> On Jul 11, 2016, at 6:18 PM, Gerriet M. Denkmann wrote:
>
>
>> On 11 Jul 2016, at 16:00, Alastair Houghton
>> wrote:
>>
>> On 11 Jul 2016, at 06:35, Gerriet M. Denkmann wrote:
>>>
>>> I have a
Cocoa-dev@lists.apple.com)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/cocoa-dev/dangerwillro
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/cocoa-dev/dangerwillrobinsondanger%40gmail.com
>
>
"What's New in Cocoa"
Sent from my iPhone
> On Jun 16, 2016, at 9:49 AM, Jeff Szuhay wrote:
>
> Tuesday?
> Any close approximation of the title of his talk would be helpful.
>
>> On Jun 15, 2016, at 4:47 PM, dangerwillrobinsondan...@gmail.com wrote:
>>
>> Watch the Ali Ozer video from the ot
uests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/cocoa-dev/dangerwillrobinsondanger%40gmail.com
>
> This email sent to dangerwillrobinsond
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/cocoa-dev/dangerwillrobinsondanger%40gmail.com
>
> This email sent to dangerwillrobinsondan...@gmail.com
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.co
LForURL for
>>>> /Users/phil/Documents/sample.txt returned error Error
>>>> Domain=NSOSStatusErrorDomain Code=-50 "paramErr: error in user parameter
>>>> list”
>>>>
>>>> My question is where in my code do I provide this paramete
Phil
>
> ___
>
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe
_
>
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/optio
t;
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/cocoa-dev/dangerwillro
)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/cocoa-dev/dangerwillrobinsondanger
_
>
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
> https://lists.
___
>
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mail
> On Apr 20, 2016, at 3:40 PM, Richard Charles wrote:
>
> The engineers at Apple that invented and implemented this stuff must have
> been amazing.
And at NeXT before that.
The folks who work and have worked on Cocoa have always included people with
broad minds, deep talent and x-ray visio
> On Apr 8, 2016, at 7:32 PM, Graham Cox wrote:
>
> By exposing the bindings that an object supports and creating an Interface
> Builder palette, you can make instances of your own classes bindable in
> Interface Builder.”
>
> If this information is still correct,
It's not.
Not since Xcode
karelia.com
>>
>> This email sent to mabdul...@karelia.com
>
>
> ___
>
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the mode
> On Apr 8, 2016, at 3:37 PM, Shane Stanley wrote:
>
> But that doesn't help with the problem of bindings for selectedIndex, does it?
The point is you create a different property that gets set by the action
method.
Bind to that property.
It reduces code but necessitates adding a comment t
It's hard to find.
asciiwwdc site makes it discoverable.
As far as I can tell it was only there (so in a video) but might be in some
release notes though those often don't show up in searches.
The programming guide docs are generally woefully out of date for controls that
don't come inside of
> On Mar 31, 2016, at 5:24 PM, a2z wrote:
>
> I need to add 'Zip' and 'Unzip' menu options to Finder. When selected it
> would launch my Application to Zip and Unzip files. I understand that I
> need to implement services for this and 'Service Implementation Guide' is
> the place to start, c
>
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
> htt
etc.).
>
> Regards,
> Ken
>
>
> ___
>
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.app
> On Mar 8, 2016, at 6:36 PM, Daryle Walker wrote:
>
> On some random Mac programming page, I saw code explicitly setting cascading
> to TRUE. I looked at that and wondered if I can do better. Since the setting
> looks like a property, I added “shouldCascadeWindows” to the User-Defined
> Runt
_
>
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update yo
___
>
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
> https://
It seems like the shorter one would be for a "click here to see more
information or open this file URL" and the longer one is for "this URL failed
to load".
But it definitely deserves a docs bug.
It might be one of those obscure things noted in some programming guide doc,
but even if it is tha
> On Feb 14, 2016, at 7:17 PM, Marcel Weiher wrote:
>
>
>> On 11 Feb 2016, at 20:44, Dan Lau wrote:
>>
>> If a file has its contents mapped using NSData's
>> initWithContentsOfFile + NSDataReadingMappedIfSafe,
>> deleting it doesn't appear to affect reading it's mapped contents. Does
>> any
t;> https://lists.apple.com/mailman/options/cocoa-dev/diederik%40tenhorses.com
>>
>> This email sent to diede...@tenhorses.com
>
> ___
>
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>
> Please do not post admin r
> On Feb 9, 2016, at 4:02 PM, Jens Alfke wrote:
>
>
>> On Feb 8, 2016, at 9:45 PM, Glenn L. Austin wrote:
>>
>> According to the docs on Reachability (possibly lost in the mists of
>> time...), Reachability isn't really designed to tell you whether your net
>> access *will* succeed, but
raw requests.
>>>
>>> Multiple invalid regions can be merged.
>>>
>>>> But there must be some place that contains a queue of upcoming draw
>>>> requests. If so, is there access to it?
>>>
>>> There really isn't any suc
apsed
>
>
>….
> }
>
>
>
> ―Graham
>
>
>
> ___
>
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the mod
> On Jan 25, 2016, at 4:01 AM, Alex Zavatone wrote:
>
> Yeah, as long as it’s an NSObject type and it’s in the class, we should be
> able to automatically get the property type of class and automatically create
> the archiver and dearchiver.
>
> Writing this stuff manually every time seems
t.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/cocoa-dev/dangerwillrobinsondanger%40gmail.com
>
> This email sent to dangerwillrobinsondan...@gmail.com
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/cocoa-
ts or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/cocoa-dev/dangerwillrobinsondanger%40gmail.com
>
> This email sent to dangerwillrobinsonda
Glad that worked. I'll also file some docs bugs.
Another way to do this is to implement a controller or container that handles
it.
View controllers are in the responder chain and can act as the item that needs
validation and set the control properties.
We can also look at the design of toolb
Yeah this was one of those little stumpers.
The control implements the methods to be eligible for being validated but
shouldn't validate itself.
A controller or something else in the responder chain that knows about app
state should do validation.
The docs should be bugged.
Sent from my iP
Oh right.
So this is a clever one.
The key in the docs might be the responder chain mentions.
The control doesn't have to validate itself.
On the contrary, usually some controller validates.
The control generally should know about state elsewhere.
Sent from my iPhone
> On Dec 14, 2015, at 6:
ts.apple.com
>
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/cocoa-dev/dangerwillrobinsondanger%40gmail.com
>
> This email sent to dangerwillrobinsondan...@gmail.com
___
Cocoa-dev mailing list (Cocoa-dev@li
lists.apple.com
>>
>> Help/Unsubscribe/Update your Subscription:
>> https://lists.apple.com/mailman/options/cocoa-dev/sevenbitstech%40gmail.com
>>
>> This email sent to sevenbitst...@gmail.com
> ___
>
> Cocoa-dev mailing
ists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/cocoa-dev/dangerwillrobinsondanger%40gmail.com
>
> This email sent to dangerwillrobinsondan...@gmail.com
___
Cocoa-dev mailing list (Coc
> On Oct 12, 2015, at 8:45 PM, Lakshmi P Shanmugam
> wrote:
>
> I'm running our application on OSX 10.11. NSGraphicsContext
> currentContext() returns nil in one of the drawing methods. The same code
> works fine on OSX 10.9.5 and 10.10.3.
> According to the documentation, currentContext ret
>
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscrip
mailing list (Cocoa-dev@lists.apple.com)
>>>
>>> Please do not post admin requests or moderator comments to the list.
>>> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>>>
>>> Help/Unsubscribe/Update your Subscription:
>>> http
__
>
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
> https://lists.app
> On Sep 30, 2015, at 3:12 PM, Jens Alfke wrote:
>
> Hey, if I liked working with JavaScript DOM APIs I’d be a web developer :-p
> I prefer languages with fancy features, like warning me if I pass the wrong
> number of parameters to a function. At build time, even.
No disagreement here. None
ocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
> https://lists.
___
>
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> H
_
>
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
> ht
led a radar for.
>
>
> ―
>
> Thank you all for the suggestions though, I will try each of them.
>
> ___
>
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>
> Please do not post admin requests or
>
> ___
>
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> He
Q&e=
> >
>
> ―Jens
> ___
>
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.app
equests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/cocoa-dev/dangerwillrobinsondanger%40gmail.com
>
> This email sent to dangerwillrobinsonda
_
>
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
&
roller,
>> and the standard behavior that returns the count is “count”. Note that the
>> table view doesn’t even know the name of the relevant property, because it’s
>> hidden on the “other” side of the array controller, not to mention buried
>> inside a binding. It’s
> On Sep 6, 2015, at 5:20 PM, Felipe Monteiro de Carvalho
> wrote:
>
> In Mac OS X maybe, but in Linux and Windows there is no problem in a
> modal window having a menu, so its not like its a conceptual problem.
No. It IS a conceptual problem.
That is not how Cocoa apps work.
Don't try to fi
> ___
>
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your S
gt; ordered.
>
>
>
> ___
>
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
t post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/cocoa-dev/dangerwillrobinsondanger%40gmail.com
>
> This email sent to dan
, so an Objective-C method that throws an exception...what happens?
>
> Also, if the method of the call site is marked as "throws," does that mean
> the error will propagate out?
>
> Pity it's not a real exception mechanism.
>
> --
> Rick Mann
> rm...@latencyze
iling list (Cocoa-dev@lists.apple.com)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.c
>
> ___
>
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscr
>>
>> Regards,
>> Ken
>
> Thanks, João
> ___
>
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-a
on all the hookers and blow
>> that are readily available within Infinite Loop.
>>
>> Again: these are widespread problems. I find examples almost
>> everywhere I look. Free Software is no exception.
>>
>> However:
>>
>> My satirical writing and
derators at cocoa-dev-admins(at)lists.apple.com
>>
>> Help/Unsubscribe/Update your Subscription:
>> https://lists.apple.com/mailman/options/cocoa-dev/rols%40rols.org
>>
>> This email sent to r...@rols.org
>
>
>
> On 2015/06/25, at 15:49, Britt Durbrow
> wrote:
>
> IMHO, named parameters at call sites are one of the things that makes
> Objective-C great; and I am VERY happy that Swift-2 enforces this.
I agree whole heartedly.
But will call out that it is a considered and thoughtful design by Cocoa a
m
>
>
>
> ___
>
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Un
Sent from my iPhone
> On 2015/06/06, at 13:12, Carl Hoefs wrote:
>
> Okay, got it. (BTW, it’s probably just me, but the entire set of CF*
> functions seems to be a bit oddly designed, no?)
They might seem so at first but they're pretty clever and well designed as an
Object Oriented C.
They'
> On 2015/05/11, at 20:41, Graham Cox wrote:
>
> Aha… I do see those. They were not the subject of the WWDC video I watched -
> maybe dangerwill was referring to a different one? These look potentially
> useful, I’ll check them out.
>
> ―Graham
You had the right video I believe. The trick i
haps I missed something germane in the discussion about why a simple
> scheme like that doesn’t fulfil all requirements.
> ___
>
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>
> Please do not post admin requests or moderator comme
rators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/cocoa-dev/dangerwillrobinsondanger%40gmail.com
>
> This email sent to dangerwillrobinsondan...@gmail.com
___
Coc
You've missed something.
NSScrollView coordinates the scrollers and the clip view total experience.
NSView is what implements the NSResponder method.
It still receives the same events that are sent from scrolling.
All the same things apply about interpreting the events that pass in to the
sc
>
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple
Sent from my iPhone
> On 2015/05/06, at 9:58, dangerwillrobinsondan...@gmail.com wrote:
>
> If you have AutoLayout on in a window it's actually on for all views.
> NSScrollView and its hierarchy are a bit weird though.
> Thing to do is create height and width constraints for the document view
Sent from my iPhone
> On 2015/05/06, at 14:14, Roland King wrote:
>
> One of the things you ‘pick up’ as you learn autolayout is that when frame
> sizes disappear to {0,0} that often means you have an ambiguous layout and
> you need more constraints.
More precisely it means a view is either
1 - 100 of 226 matches
Mail list logo
