Re: [moose-devel] Can't get moose.connect to work

[Subhasis R. <ray...@gm...>]

Dear Dilawar,
  There was an update in naming convention which has not been reflected in
the pulsegen demo:

    moose.connect(tab, 'requestOut', pg, 'getOutput')

should be

    moose.connect(tab, 'requestOut', pg, 'getOutputValue')

I have committed this change to svn repo. Please update your copy. Also, in
general the naming convention is that if there is a src field called
output, then its counterpart value field is outputValue.



Best,
- Subhasis
(  ʃʊbʱaːʃɪʃ )


On Sun, Mar 9, 2014 at 12:18 AM, Dilawar Singh <dil...@nc...> wrote:

> I am running Demo/snippets/pulsegen.py file with async branch. On line 64,
> following line is causing problem.
>
>     tab = moose.Table('tab')
>     m = moose.connect(tab, 'requestOut', pg, 'output', 'Single')
>
> I have tried changing srcField (requestOut) many times and even printing
> all
> possible srcField. But it always fails with following error message:
>
>      Shell::doAddMsg: Error: Src/Dest Msg type mismatch: requestOut/output
>
> There is virtual function `checkTarget` which checks for type mismatch,
> but it
> is returning 0 in every case. The comment on top of the virual function
> says,
>
>      Is called only from msg src, so most Finfos return 0.
>
> Is there a note or some writeup which summarises how to set-up connection
> in
> async branch.
>
> --
> Dilawar
>
>
> ------------------------------------------------------------------------------
> Subversion Kills Productivity. Get off Subversion & Make the Move to
> Perforce.
> With Perforce, you get hassle-free workflows. Merge that actually works.
> Faster operations. Version large binaries.  Built-in WAN optimization and
> the
> freedom to use Git, Perforce or both. Make the move to Perforce.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
> _______________________________________________
> moose-devel mailing list
> moo...@li...
> https://lists.sourceforge.net/lists/listinfo/moose-devel
>