Sorry, forgot the last part. After you get the components using the calendar you wish to use with your two dates, then call NSDateComponentsFormatter. For a simple case, you could get by with: +

Ooops, I’m wrong... Leap year complications should be part of the time interval and be ignored. My programming history got the better of my knowledge... the first ever COBOL program I wrote

Use NSCalendar’s method: - (NSDateComponents *)components:(NSCalendarUnit)unitFlags fromDate:(NSDate *)startingDate toDate:(NSDate *)resultDate options:(NSCalendarOptions)opts; -- Gary L.

Can not be done accurately using only a Time Interval in seconds. You also need either the start or end date to figure out leap year complications. Don’t know of any. I’d probably roll my

There's NSDateComponentsFormatter, although it's fairly limited. -- Shane Stanley <sstanley@...> <www.macosxautomation.com/applescript/apps/>, <latenightsw.com>

Look at the NSDate and NSDateFormatter classes. -Owen

Objective-C, Mac. Hi, I’m trying to display a countdown to a date in the future e.g. the number of years, weeks and days to 1/1/2021. I have the Time Interval between now and the future date in

What do you have to do these days to make this work? I tried returning YES from acceptsFirstResponder, as was suggested somewhere. There is 1 NSTrackingArea added to the view, using options

Yes, I did mean if there was currently a way to do it, but then I meandered over to "wouldn't it be great" territory. I've submitted radar://50687965 for this feature suggestion. I was also thinking

If you're logging a feature request, I'd be delighted to back it. But when you said "is", I presumed you meant present tense. -- Shane Stanley

Well, one could say the Info.plist is just a an xml file that gets added to the bundle, but it can be preprocessed. I use that feature a lot, like so the version number only has to be defined in one

If there's another way, I don't know it. It's just an XML file that gets added straight to the bundle, so I don't see how that would work. -- Shane Stanley

I did just find makeScriptingObjectOfClass or whatever it is (not at my desk now), so that’s a good way to ignore readonly properties. Still, seems like something should be doing that when letting

This seems like bug, or I need to override something. I have a class: @interface Blah : NSObject @property (readonly) NSUInteger id; @end The id property is exposed to AppleScript in the Blah

What? I think you misunderstood. This is purely AppleScript communication. Bill and Shane already confirmed I'm doing the right thing. -- Steve Mills Drummer, Mac geek

How do you plan to consume it? As an array, dictionary? You can even save it out as a pList and read it off media if you wish. You can even serialize it to JSON or XML. There even is serializing

OK, thanks for the confirmation. I was hoping there was something analogous to -objectSpecifier that I wasn't finding, such as -valueDdescriptor that would be called on the key-value object found at

Oops, yes. This was on the crash in dragImageForSelection. Jens Alfke wrote on 6/5/19 20:02: -- John Brownie Mussau-Emira language, New Ireland Province, Papua New Guinea Kouvola, Finland

if I follow you correctly, that sounds about right. Cocoa scripting doesn't like simple records -- it wants custom record types. -- Shane Stanley

I can’t add much other than I recall yours was the solution I used too. Off-Topic WWDC is very close and I’d be surprised if there aren’t significant changes to the whole Scripting shambles (I