Note that there are some explanatory texts on larger screens.

plurals
  1. POproblem passing multiple parameters
    primarykey
    data
    text
    <p>[EDIT] ===PROBLEM SOLVED====</p> <p>====JUST AFTER I SUBMITTED I SAW THE OBVIOUS====</p> <p>Wrong name in the call "andUpdate", should be "andWriteRead:". Just realize i am a blind person.</p> <p>Hi,</p> <p>I am passing multiple parameters in messages in other parts of my code without problem but with this i have problem. It works perfectly passing one parameter but not with two. I would guess it is just me who doesn't see the forrest because of the trees. Could someone please look at this and tell me what i am doing wrong? </p> <p>The following works:</p> <p>message:</p> <pre><code>[setupQuestions questionsNumbersPLIST:diffLvls]; </code></pre> <p>Target object.</p> <p>.h:</p> <pre><code>- (void)questionsNumbersPLIST:(NSMutableArray *)questionsList; </code></pre> <p>.m:</p> <pre><code>- (void)questionsNumbersPLIST:(NSMutableArray *)questionsList { </code></pre> <blockquote> <p>=========================================</p> </blockquote> <p>Then i try to pass multiple parameters like this:</p> <p>message:</p> <pre><code>[setupQuestions questionsNumbersPLIST:diffLvls andUpdate:myString]; </code></pre> <p>Target object</p> <p>.h:</p> <pre><code>- (void)questionsNumbersPLIST:(NSMutableArray *)questionsList andWriteRead:(NSString *)update; </code></pre> <p>.m:</p> <pre><code>- (void)questionsNumbersPLIST:(NSMutableArray *)questionsList andWriteRead:(NSString *)update; </code></pre> <p>I get:</p> <blockquote> <p>warning: (Messages without a matching method signature</p> </blockquote>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload