WATask calling another WATask

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

WATask calling another WATask

Mariano Martinez Peck
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
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: WATask calling another WATask

Johan Brichau-2
Mariano,

So it's not a Gemstone specific issue? You also have it in Pharo?
Or not?

It sounds familiar to https://code.google.com/p/seaside/issues/detail?id=744

gotta run now but I'm online later on...
Johan

On 10 Jun 2014, at 17:39, Mariano Martinez Peck <[hidden email]> wrote:

> 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
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: WATask calling another WATask

Karsten Kusche
have you had a look at WATaskNotDelegate>>seasidePossibleCauses?

Kind Regards
Karsten

-- 
Karsten Kusche - Dipl. Inf. (FH) - [hidden email]
Georg Heeg eK - Köthen
Handelsregister: Amtsgericht Dortmund A 12812 

Am Dienstag, 10. Juni 2014 um 17:48 schrieb Johan Brichau:

Mariano,

So it's not a Gemstone specific issue? You also have it in Pharo?
Or not?


gotta run now but I'm online later on...
Johan

On 10 Jun 2014, at 17:39, Mariano Martinez Peck <[hidden email]> wrote:

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
_______________________________________________
seaside mailing list

_______________________________________________
seaside mailing list


_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: WATask calling another WATask

Mariano Martinez Peck
In reply to this post by Johan Brichau-2



On Tue, Jun 10, 2014 at 12:48 PM, Johan Brichau <[hidden email]> wrote:
Mariano,

So it's not a Gemstone specific issue? You also have it in Pharo?
Or not?

It sounds familiar to https://code.google.com/p/seaside/issues/detail?id=744


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: method. 
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 right?

Thanks,
 
gotta run now but I'm online later on...
Johan

On 10 Jun 2014, at 17:39, Mariano Martinez Peck <[hidden email]> wrote:

> 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
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside



--
Mariano
http://marianopeck.wordpress.com

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: WATask calling another WATask

Mariano Martinez Peck
In reply to this post by Karsten Kusche



On Tue, Jun 10, 2014 at 12:54 PM, Karsten Kusche <[hidden email]> wrote:
have you had a look at WATaskNotDelegate>>seasidePossibleCauses?


Thanks Karsten, I wasn't aware of that method. It might be this item:  

'The Task is embedded in another Component but has not been included in the list of child Components returned by the Component''s #children method.' 

But not fully true because my sub-task was NOT embedded...right?
 
Kind Regards
Karsten

-- 
Karsten Kusche - Dipl. Inf. (FH) - [hidden email]
Georg Heeg eK - Köthen
Handelsregister: Amtsgericht Dortmund A 12812 

Am Dienstag, 10. Juni 2014 um 17:48 schrieb Johan Brichau:

Mariano,

So it's not a Gemstone specific issue? You also have it in Pharo?
Or not?


gotta run now but I'm online later on...
Johan

On 10 Jun 2014, at 17:39, Mariano Martinez Peck <[hidden email]> wrote:

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
_______________________________________________
seaside mailing list

_______________________________________________
seaside mailing list


_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside




--
Mariano
http://marianopeck.wordpress.com

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside