Re: How are email apps written in iOS?

> On Nov 10, 2015, at 7:37 PM, Nicholas Acosta > wrote: > > Sent from my iPad hi, I have been wondering how to write a email app for iOS. > I have been searching the technologies in iOS and don't know what framework > to use. Would I use the message you I framework for this? Thank you. Messa

How are email apps written in iOS?

Sent from my iPad hi, I have been wondering how to write a email app for iOS. I have been searching the technologies in iOS and don't know what framework to use. Would I use the message you I framework for this? Thank you. ___ Cocoa-dev mailing list

Re: The joys of people using valueForKey to get objects out of a dictionary.

> On Nov 10, 2015, at 15:21, Alex Zavatone wrote: > > >> Yeah. Honestly, I'm looking for cases that would justify why all the >> dictionary object access blocks in this code that use valueForKey are >> wrapped with @try/@catch clauses. I've never seen cases with objectForKey >> that would

Re: Storing files into the Documents folder

> On Nov 10, 2015, at 1:54 PM, Samuel Williams > wrote: > > A while ago I seem to recall reading on Apple's documentation that > applications storing log files, save games, and other related data-files > automatically into ~/Documents/ was not recommended IMHO you shouldn’t hardcode writing an

Re: Storing files into the Documents folder

On Nov 10, 2015, at 13:54 , Samuel Williams wrote: > > Can anyone give me advice about this > and point me to the official information from Apple? You can start here: https://developer.apple.com/library/prerelease/mac/documentation/FileManagement/Conceptual/FileSystemProgrammingGuide/

Re: The joys of people using valueForKey to get objects out of a dictionary.

> Le 10 nov. 2015 à 19:52, Alex Zavatone a écrit : > > > On Nov 10, 2015, at 12:35 PM, Greg Weston wrote: > >> >> >>> It's been about 4 or 5 years since I made this mistake but I've just seen a >>> massive swath of code where every access of a dictionary object is using >>> valueForKey ins

Storing files into the Documents folder

A while ago I seem to recall reading on Apple's documentation that applications storing log files, save games, and other related data-files automatically into ~/Documents/ was not recommended, but I can't seem to find that advice now when searching. Can anyone give me advice about this and point me

Re: The joys of people using valueForKey to get objects out of a dictionary.

Lots of stuff with that. An immutable dictionary can't be changed. Someone doesn't know how to spell unknown (NSUnknosnKeyException). And not sure if that period is part of the key username or just good English, but if given as part of the key, it becomes a key path with an empty key. Anyway, th

Re: The joys of people using valueForKey to get objects out of a dictionary.

And you guys have no idea how useful this discussion was to me today. Even though the KVO valueForKey: method doesn't crater with an NSUnknownException with ease, it turns out that this wonderful code is also using the KVO method of setValue: forKey: on a dictionary. And guess what? *** Termin

Re: NSSegmentedControl's sizing behaviour

Thanks Ken, that works fine. Eyebrows a little bit raised that this is needed, but then segmented controls are horrible to deal with in any case. —Graham > On 10 Nov 2015, at 3:35 PM, Ken Thomases wrote: > > On Nov 9, 2015, at 9:36 PM, Graham Cox wrote: >> >> I’m struggling to get the beh

Re: The joys of people using valueForKey to get objects out of a dictionary.

On Nov 10, 2015, at 2:15 PM, Jens Alfke wrote: > >> On Nov 10, 2015, at 10:52 AM, Alex Zavatone wrote: >> >> Here's a great reason to use objectForKey: wherever possible instead of >> valueForKey: - valueForKey: with an unknown key will throw >> NSUnknownKeyException saying "this class is no

Re: The joys of people using valueForKey to get objects out of a dictionary.

On Nov 10, 2015, at 10:52 , Alex Zavatone wrote: > > For what we're doing on a daily basis, if we're not using @ within our keys, > I still can't see anything concrete besides "objectForKey is an NSDictionary > method" while "valueForKey is a KVO method". You don’t really have to agonize over

Re: The joys of people using valueForKey to get objects out of a dictionary.

> On Nov 10, 2015, at 10:52 AM, Alex Zavatone wrote: > > Here's a great reason to use objectForKey: wherever possible instead of > valueForKey: - valueForKey: with an unknown key will throw > NSUnknownKeyException saying "this class is not key value coding-compliant > for the key ". Yes, but

Best practice for adjusting UIScrollView contentOffset in 'willTransitionToTraitCollection'

I have a UIScrollView scrolled to the bottom of content - so the content bottom is at the bottom of the view - in a compact environment. When the view rotates to regular, the contentOffset is too large - so the bottom of the content appears in the middle of the view. Without hard coding nav b

Re: The joys of people using valueForKey to get objects out of a dictionary.

On Nov 10, 2015, at 12:35 PM, Greg Weston wrote: > > >> It's been about 4 or 5 years since I made this mistake but I've just seen a >> massive swath of code where every access of a dictionary object is using >> valueForKey instead of objectForKey. >> >> I've got a few examples of why this is

Re: The joys of people using valueForKey to get objects out of a dictionary.

> On Nov 10, 2015, at 8:32 AM, Alex Zavatone wrote: > > It's been about 4 or 5 years since I made this mistake but I've just seen a > massive swath of code where every access of a dictionary object is using > valueForKey instead of objectForKey. > > I've got a few examples of why this is a "r

Re: The joys of people using valueForKey to get objects out of a dictionary.

> On Nov 10, 2015, at 8:32 AM, Alex Zavatone wrote: > > It's been about 4 or 5 years since I made this mistake but I've just seen a > massive swath of code where every access of a dictionary object is using > valueForKey instead of objectForKey. > > I've got a few examples of why this is a "r

Re: UINavigationController, hidesBarsWhenVerticallyCompact, and "unhandled taps" - how to "handle" them

> On Nov 10, 2015, at 7:46 AM, David Hoerl wrote: > > Title pretty much says it - I have a UICollectionView, > hidesBarsWhenVerticallyCompact = true. Rotate to hide the nav bar works fine. > > I can press and drag to scroll, no change. But if I tap on a cell, even if my > code "handles the ta

Re: The joys of people using valueForKey to get objects out of a dictionary.

> It's been about 4 or 5 years since I made this mistake but I've just seen a > massive swath of code where every access of a dictionary object is using > valueForKey instead of objectForKey. > > I've got a few examples of why this is a "really bad idea"™, I would like to see these examp

10.11: NSDatePicker cuts off year digit

Hi, I have an app with an NSDatePicker in small control size, date only format (day/month/year) and stepper controls. On El Capitan, with certain year numbers, the control cuts off the last digit, for instance with 1966, 1969 and 1999. The control displays the first 3 digits only ("196", "19

Re: The joys of people using valueForKey to get objects out of a dictionary.

> On 2015/11/10, at 8:32, Alex Zavatone wrote: > > It's been about 4 or 5 years since I made this mistake but I've just seen a > massive swath of code where every access of a dictionary object is using > valueForKey instead of objectForKey. > > I've got a few examples of why this is a "really

Re: The joys of people using valueForKey to get objects out of a dictionary.

> On Nov 10, 2015, at 8:32 AM, Alex Zavatone wrote: > > Looking for reasons why I can explain "yeah, I know it works, but here's why > it's a terrible idea to use to access a dictionary's objects". I don’t know any reason why it would be bad, although I don’t typically use it. On a related no

Re: The joys of people using valueForKey to get objects out of a dictionary.

> On 10 Nov 2015, at 16:32, Alex Zavatone wrote: > > It's been about 4 or 5 years since I made this mistake but I've just seen a > massive swath of code where every access of a dictionary object is using > valueForKey instead of objectForKey. > > I've got a few examples of why this is a "real

The joys of people using valueForKey to get objects out of a dictionary.

It's been about 4 or 5 years since I made this mistake but I've just seen a massive swath of code where every access of a dictionary object is using valueForKey instead of objectForKey. I've got a few examples of why this is a "really bad idea"™, and certainly might explain why lots of that cod

UINavigationController, hidesBarsWhenVerticallyCompact, and "unhandled taps" - how to "handle" them

Title pretty much says it - I have a UICollectionView, hidesBarsWhenVerticallyCompact = true. Rotate to hide the nav bar works fine. I can press and drag to scroll, no change. But if I tap on a cell, even if my code "handles the tap" by implementing the collection view delegate, the nav bar s

Re: Another AppleScript-ObjC Bridge Question

Hi Again Shane, Got it now, thanks a lot for this. All the Best Dave ___ 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

Re: Another AppleScript-ObjC Bridge Question

On 10 Nov 2015, at 9:46 PM, Dave wrote: > > Just to clarify, I don’t need a “_” at all, anywhere? No. > The reason I added them is because in uses them in the example at: That's pre-10.9 syntax. Open Script Editor, and enter the code you see there: on square_(aNumber) return aNumb

Re: Another AppleScript-ObjC Bridge Question

Thanks Shane, Just to clarify, I don’t need a “_” at all, anywhere? The reason I added them is because in uses them in the example at: http://appscript.sourceforge.net/asoc.html Thanks a Lot and All the Best Dave > On 9 Nov 2015, at 22:47, Shane S