Jeff, So what you’re suggesting is… 1. Define a template implementation 2. Associate each selector pattern with that implementation That seems like it should work. I’ll give it a try and let

In the designated initialise of your Parser class, you can use class_addMethod to add whatever you like to your instance's

Jeff, Thanks for the idea… it might be a good choice… as for additional details. The caller can be seen as a controller. It dynamically allocates model (parser) classes based on context. The

You really haven't provided enough information about the caller, and you've skipped over the C programmers favourite answer.Presumably you actually NEED all those seperate selectors and can't just

Gary, interesting… I’ll have to see if Returning an NSValue wrapped scalar translates to the scalar result on the other side when I call -getReturnValue: Thanks! Sandor

Alex, I am proposing letting the runtime handle the fact the object does not respond to the selector. So, under this assumption I am inside one of two methods: -doesNotRespondToSelector: or

You might want to consider using valueForUndefinedKey: and parse it to know which value you care about, and then return the value through NSValue, which can encapsulate any value, although a

Well, I’m guessing here, but can’t you construct the method and use a perform selector, get the result and return it? It seems like you are making methods, performing them, then need to perform

Alex, Thanks for the idea. I not sure how that helps me get the return value back to the original caller. Am I missing your point? Here’s more details, in pseudo code // Controller class SEL

Would it be possible to put them in an array or dictionary as NSStrings and use performSelector on one of them if it is present within the array or dict?

I have a certain group of selectors that all follow a strict naming convention, -(Status)parseXYZ -(Status)parseRST All have one line that does the same thing and return a scalar (enum) as a

The action name is part of the “view” layer in model-controller-view architecture. But most of the actual undoable ’stuff’ is in the model. So I usually set the action name at the top level

As usual, the answer was staring me in the face. The old code was synchronous, the new is asynchronous. I was restoring the view after the call to -dragImage… because that used to keep control

Hi all, I’m updating some legacy code that currently uses the ‘classic’ way to drag stuff, namely [NSView dragImage:at:offset:event:pasteboard:source:slideBack:]; This code has been

Thanks — it is a bit kludgey, but might do in a pinch, as you say. In some cases I can set a flag on my drawing to tell it that the context should be a PDF at that time, since I am responsible for

I played around with it and found that bitmap (easy to create) and PDF contexts have the same CFTypeID so no help there, and that there doesn’t appear to be a public context [sub-]type property. One

I need to determine whether I am drawing into a CGPDFContext or a different context at runtime. In AppKit, I can use [NSGraphicsContext currentContextDrawingToScreen], but this is code that is passed

I have a CoreData-based app where I am experimenting with inter-device synchronization using iCloudKit. At the moment, I am running in Development mode and am using an iPad and a MacCatalyst app as

Screw it. I've switched the migration progress window to a regular window and now present it modally. This kind of window WILL appear during state restoration, unlike a palette which has been sent

I needed to add many attributes to my CoreData model. Filling in these attributes will happen during migration of old docs, which means loading all the files that each asset points to. Since it can