<body><div id="__MailbirdStyleContent" style="font-size: 12pt;font-family: calibri;color: #000000">
Hmm... maybe "Project current world displayWorldSafely"? Or for a single morph "Display getCanvas fullDraw: self"? Well, the latter does ignore Z-Order and occlusion and stuff.<div><br></div><div>Best,</div><div>Marcel</div><div class="mb_sig"></div><blockquote class="history_container" type="cite" style="border-left-style:solid;border-width:1px; margin-top:20px; margin-left:0px;padding-left:10px;">
<p style="color: #AAAAAA; margin-top: 10px;">Am 15.01.2018 22:37:52 schrieb tim Rowledge <tim@rowledge.org>:</p><br>> On 15-01-2018, at 1:17 PM, Eliot Miranda <eliot.miranda@gmail.com> wrote:<br>> <br>> Hi Tim,<br>> <br>> On Mon, Jan 15, 2018 at 10:41 AM, tim Rowledge <tim@rowledge.org> wrote:<br>> For something that cpu intensive how about sticking a deliberate yield in the cycle somewhere so the rest of the system can do some work? That would help provide some chance of catching an interrupt key, something I faintly recall being a bit of a pain under the sim.<br>> <br>> Perhaps a yield in the sim code for the process check?<br>> <br>> The right place is in ioForceDisplayUpdate, which in the simulator is a no-op, but is called in all the right places (after deferDisplayUpdates is reset for example).<br><br>True, but I was wondering about having a yield to allow the wider system a play with the cpu. That may or may not be desirable, depending on what’s happening. Actually I guess that might be better done with a high-priority timer to interrupt and faff around.<br><br>> <br>> <br>> The classic simple approach is #doOneCycle, assuming morphic is in use. If you want to get all low-level and brutal you could use DisplayScreen>>#forceToScreen I guess.<br>> <br>> So what I don't see is why doOneCycle is the right call. That advances the animation clock,<br><br>It’s just the more-or-less habitual response and it let’s other morphs update; again, maybe desirable if you were to have a bunch of monitoring morphs that displayed cycles, interrupts, gc data etc.<br><br>> whereas what I want to do is simply ensure that a form submorph in a window appears on screen. I'm happy to use doOneCycle if that's the right thing but reading the code it seems to have far more effects than I want.<br><br>Sounds like whacking DisplayScreen>>#forceToScreen would be where you want to start for now<br><br>tim<br>--<br>tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim<br>Strange OpCodes: PNG: Pass Noxious Gas<br><br><br><br></tim@rowledge.org></eliot.miranda@gmail.com>
</blockquote>
</div></body>