[Seaside] WATask calling another WATask
Mariano Martinez Peck
marianopeck at gmail.com
Tue Jun 10 16:51:21 UTC 2014
On Tue, Jun 10, 2014 at 12:48 PM, Johan Brichau <johan at inceptive.be> wrote:
> So it's not a Gemstone specific issue? You also have it in Pharo?
> Or not?
> It sounds familiar to
Thanks Johan for the point. In fact, it's that exact situation. I tried
both recommendations from Julian from the issue tracker.
The first one is storing the the sub-task as an instVar rather than temp
var and add it to #children. The second was changing the #visitTask:
To avoid code modification I went with first option. However...I still
consider this a bug since #children (and move the sub-task from temp to
instVar) should NOT be necessary from a user point of view in this case
> gotta run now but I'm online later on...
> On 10 Jun 2014, at 17:39, Mariano Martinez Peck <marianopeck at gmail.com>
> > Hi guys,
> > I have a strange situation. I have a main WATask subclass called XXX. In
> XXX's #go I do a #call: to another task YYY and I get a
> "WATaskNotDelegated: This task has no delegation.". Of course, I put a halt
> in YYY's #go and it does not halt at all. It seems task XXX is trying to
> RENDER task YYY.
> > What is even more funny, is that if in XXX instead of directly calling
> task YYY, I do a #call: to another regular WAComponent, I get the answer
> and then I call task YYY, that works!!!!
> > Any idea what could be the problem? Are tasks allowed to do a #call: to
> other tasks?
> > Thanks in advance,
> > --
> > Mariano
> > http://marianopeck.wordpress.com
> > _______________________________________________
> > seaside mailing list
> > seaside at lists.squeakfoundation.org
> > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> seaside mailing list
> seaside at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside