Hi,<div><br></div><div>I am having the exact same problem with an Iliad app, which stopped working in 1.3 because it loses the context when catching an announcement.��I&#39;d really love to know the solution to this, in the Iliad list we didn&#39;t manage to fix it.</div>

<div><br></div><div>Cheers,</div><div><br><div class="gmail_quote">2011/7/18 Norbert Hartl <span dir="ltr">&lt;<a href="mailto:norbert@hartl.name">norbert@hartl.name</a>&gt;</span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

<br>
Am 17.07.2011 um 22:06 schrieb St��phane Ducasse:<br>
<div class="im"><br>
&gt;&gt; It is just that everybody should be aware of the problem and have its own &quot;simple&quot;<br>
&gt;&gt; announcements when using any of the frameworks above.<br>
&gt;<br>
&gt; you know that this is not the good solution. So probably it was a bad idea to catch<br>
&gt; everything and probably UnhandledError is a better choice.<br>
&gt; Now again without feedback we will just progress but much slower.<br>
<br>
</div>Why is the usage of on:fork: not an option of the Announcer? We don&#39;t have one single Announcer in the system so I don&#39;t see the need why they should behave all the same. Over time I think there will be multiple announcers in the system that have different impact in case something goes wrong. For the core announcers on:fork: is probably a good idea to preserve consistency in the system.<br>


For the rest it may be better to preserve stack to be able to debug and to reduce side effects. I think on:fork is targetted to an edge case so it should not be the default.<br>
<br>
my 2 cents,<br>
<font color="#888888"><br>
Norbert<br>
</font></blockquote></div><br><br clear="all"><br>-- <br>Bernat Romagosa.<br>
</div>