Changes with announcements ?
Locked
 
|
Hello,
Today I experimented some strange behaviours with announcements that I didn't have in some previous moose images. I think that there was some changes related to announcements in pharo recently, but I could not be sure it is related.
At one point in my code I have: browser on: AnnouncementClass send: #actionSelector browser announce: anAnnouncementClass. .... .... I have the feeling that sometimes #actionSelector is executed asynchronously from the rest the code below 'browser announce: ...' . Not sure but there is maybe something with exception signals. If any signal is emited in #actionSelector it will not execute the rest of the method.
I was at leat able to write a test that do not pass in latest dev Gofer new squeaksource: 'DelaunayTmpStuffs';
package: 'ExampleAnnouncementProblems'; load. will not pass with: http://ci.moosetechnology.org/job/moose-latest-dev/402/artifact/moose_suite-4_5_dev.zip
will pass with: http://ci.moosetechnology.org/job/moose-latest-dev/393/artifact/moose_suite-4_5_dev.zip _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
I entered an Issue: http://code.google.com/p/moose-technology/issues/list?thanks=635&ts=1306418412
2011/5/26 Cyrille Delaunay <[hidden email]> Hello, _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
In reply to this post by cdelaunay
I had to fix the Mondrian class MOAnnouncer, which inherits from Announcer. But I haven't experienced what you are reporting.
Cheers, Alexandre On 26 May 2011, at 09:58, Cyrille Delaunay wrote: > Hello, > > Today I experimented some strange behaviours with announcements that I didn't have in some previous moose images. > I think that there was some changes related to announcements in pharo recently, but I could not be sure it is related. > > At one point in my code I have: > > browser on: AnnouncementClass send: #actionSelector > browser announce: anAnnouncementClass. > .... > .... > > I have the feeling that sometimes #actionSelector is executed asynchronously from the rest the code below 'browser announce: ...' . > Not sure but there is maybe something with exception signals. If any signal is emited in #actionSelector it will not execute the rest of the method. > > I was at leat able to write a test that do not pass in latest dev > > Gofer new > squeaksource: 'DelaunayTmpStuffs'; > package: 'ExampleAnnouncementProblems'; > load. > > > will not pass with: http://ci.moosetechnology.org/job/moose-latest-dev/402/artifact/moose_suite-4_5_dev.zip > will pass with: http://ci.moosetechnology.org/job/moose-latest-dev/393/artifact/moose_suite-4_5_dev.zip > > > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Re: Changes with announcements ?
|
|
Hi Cyrille,
I looked over the example, and I do not have enough knowledge to understand where the problem is. I think it would be better to post this on the Pharo mailing list, because it is not specific to Moose. Cheers, Doru On 26 May 2011, at 17:31, Alexandre Bergel wrote: > I had to fix the Mondrian class MOAnnouncer, which inherits from Announcer. But I haven't experienced what you are reporting. > > Cheers, > Alexandre > > > On 26 May 2011, at 09:58, Cyrille Delaunay wrote: > >> Hello, >> >> Today I experimented some strange behaviours with announcements that I didn't have in some previous moose images. >> I think that there was some changes related to announcements in pharo recently, but I could not be sure it is related. >> >> At one point in my code I have: >> >> browser on: AnnouncementClass send: #actionSelector >> browser announce: anAnnouncementClass. >> .... >> .... >> >> I have the feeling that sometimes #actionSelector is executed asynchronously from the rest the code below 'browser announce: ...' . >> Not sure but there is maybe something with exception signals. If any signal is emited in #actionSelector it will not execute the rest of the method. >> >> I was at leat able to write a test that do not pass in latest dev >> >> Gofer new >> squeaksource: 'DelaunayTmpStuffs'; >> package: 'ExampleAnnouncementProblems'; >> load. >> >> >> will not pass with: http://ci.moosetechnology.org/job/moose-latest-dev/402/artifact/moose_suite-4_5_dev.zip >> will pass with: http://ci.moosetechnology.org/job/moose-latest-dev/393/artifact/moose_suite-4_5_dev.zip >> >> >> >> >> _______________________________________________ >> Moose-dev mailing list >> [hidden email] >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- www.tudorgirba.com "We can create beautiful models in a vacuum. But, to get them effective we have to deal with the inconvenience of reality." _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
«
Return to Moose
|
1 view|%1 views
| Free forum by Nabble | Edit this page |