<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jun 30, 2014 at 12:54 PM, tim Rowledge <span dir="ltr"><<a href="mailto:tim@rowledge.org" target="_blank">tim@rowledge.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=""><br>
On 30-06-2014, at 12:52 PM, Chris Muller <<a href="mailto:asqueaker@gmail.com">asqueaker@gmail.com</a>> wrote:<br>
<br>
><br>
> We probably need to decide whether we want #flash to be a debugging tool or something any morph should be able to do in a way that properly integrates with the Morphic framework...<br>
><br>
> It seems we want it fairly often-enough as a IDE tool, I wouldn't be opposed to a small delay...<br>
><br>
><br>
</div>Seems pretty obvious to me - add a #slowFlashAlert method and leave the plain flash alone.<br></blockquote><div><br></div><div>-1. flash is supposed to be visible and on today's machinery it often isn't. So it's broken. I second Bert's suggestion of using alarms for a non-blocking implementation.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
tim<br>
--<br>
tim Rowledge; <a href="mailto:tim@rowledge.org">tim@rowledge.org</a>; <a href="http://www.rowledge.org/tim" target="_blank">http://www.rowledge.org/tim</a><br>
"Bother" said Pooh, as his trigger finger tired.<br>
<br>
<br>
<br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>best,<div>Eliot</div>
</div></div>