Hmm. I did try it in a playground before I posted, and the output is there. (Xcode 9.3) Does it persist if you quit and relaunch Xcode?

Many, many thanks. One curiosity, though... that works in my application but I still get no output in the Playground sample code. Marc

It’s you, but you can plausibly blame it on Swift. You need: (since ‘value(forKey:)’ needs an Obj-C property name).

This simple little playground doesn’t print any value for the last line. It is a minimization of an issue I’m having in a larger program where the key-value can not be found. Is it me (likely)

Seems not to work in Xcode Version 9.3 (9E145). Also: this is really something Xcode should to for me. Kind regards, Gerriet.

I would suggest you use a regular space, since a menu item can’t word-wrap onto a new line. It *might* make a difference if the font specifies a different width for the non-breaking space than a

Thanks a lot for this link! Looking at the German stuff, I see that for example “Print…” gets translated: 29 times: "Drucken …" NO-BREAK SPACE; HORIZONTAL ELLIPSIS 56 times: “Drucken …"

https://developer.apple.com/download/more/?name=Glossaries -- Gary L. Wade http://www.garywade.com/

https://download.developer.apple.com/Developer_Tools/Xcode_9.3/Xcode_9.3.xip

It seems like there ought to be, but I don’t think there is. I would assume that menu items that get added to your app at runtime (e.g. the ones at the bottom of the Edit menu) will be localized for

I am trying to make an macOS app international. On thing is MainMenu.strings. This contains lots of stuff which must have an official translation (e.g. into German) already. (e.g. Edit → Cut). Is

Hi Again, Yes, that is what is does in effect, the outer while loop is "while ([[NSThread currentThread] isCancelled] == NO)” which does the same thing. It only processes the Object if there is

Dave, See below for what I'm talking about with the -wait call... Additionally, think about where your testing -isCancelled and breaking out of the loop(s); you have multiple loops. Does that break,

Hi Again Sandor, Yes, I’ve had similar fun doing the same thing here! Thanks for the heads up on isCancelled and I’ll take your advice and store it as a property. I’m not sure I understand

Regarding the call to -isCancelled in the consumer thread... presumably you will have a handle to this thread somewhere and want to -cancel it gracefully prior to termination... Or cancel it and

Dave, That's great I'm glad it's working! I had fun working up the sample... :) I let it run for a couple of hours watching the processes add a consume data. It was interesting to see how the

Hi, Thanks for the sample code Sandor, I’ve now got it working correctly now and I’m really pleased with it. I realised what was wrong just before I went to sleep last night and just added the

Dave, Using NSCondition this is how I had envisioned it done. Note difference in enclosing scope of the NSCondition and loops in the processing of the objects to be consumed... Sandor

Hi All, I’ve almost got my threaded Consumer/Producer Working using NSThread and friends. However, under certain circumstances, I’m getting objects “stuck” on the queue and the Consumer thread

Yes, it has to do with autorelease, but there are usually options for getting a non-autoreleased version, e.g. usually an init method to create it, however you are (were) stuck with an released