« Return to Thread: problem getting arguments for perform:withArguments:

Re: problem getting arguments for perform:withArguments:

by mattfuchs :: Rate this Message:

Reply to Author | View in Thread

Georg:

Thanks for your reply, but that wasn't actually my problem.  After carefully
following the debugger I realized that:
1) the selector name is expected to end in a colon (:)
2) the name should be followed by a list of arguments giving the number of
arguments the receiver is expecting.  Each arg name should start with a colon.

So, to get two arguments, my selector should have been something like:

#msg::a:b

Actually, the system doesn't really examine the arg names, so it could just as
easily be:

#msg:::

I actually looked at the code counting the colons.  I suspected this was a noob
question.

Matthew

-------------------------

Hi Matthew,

I sent a tutorial some time back - it shows a 'framework' for the input/output
to the island. I forwarded you the mail separately.

The mechanism is not easy or simple, but it works.

Hope that helps!
Georg

On Fri, Apr 25, 2008 at 9:38 AM, <mattfuchs@...> wrote:

    I am trying to get information out of an island using signal:withArguments:
to
    an outside object waiting with perform:withArguments:

    More precisely I have a tObject with a tFarRef and some outside object,
obj.

    I do

    obj runScript: #selector when: {tFarRef . #msg}.

    and then have a perform:withArguments: method for obj.

    Later tObject is called with:

    self signal: #msg withArguments: #('1234').

    obj's perform:withArguments: method gets called with #selector, but
    withArguments gets #().

    The doc seems to say this is the only way to get info out of an island, but
    it's not getting any info out.  How do I get information from tObject to
obj?

    Thanks,

    Matthew

 « Return to Thread: problem getting arguments for perform:withArguments:

LightInTheBox - Buy quality products at wholesale price