[Vm-dev] Another NuScratch issue
Yoshiki.Ohshima at acm.org
Sat Nov 21 17:42:12 UTC 2020
On Sat, Nov 21, 2020 at 9:32 AM Yoshiki Ohshima <Yoshiki.Ohshima at acm.org>
> On Fri, Nov 20, 2020 at 5:11 PM Yoshiki Ohshima <Yoshiki.Ohshima at acm.org>
>> On Fri, Nov 20, 2020 at 4:50 PM tim Rowledge <tim at rowledge.org> wrote:
>>> > On 2020-11-20, at 3:10 PM, Yoshiki Ohshima <Yoshiki.Ohshima at acm.org>
>>> > So I built a new VM with a fix for the input method change. I did
>>> not fully test the other things but Scratch on the VM does not do
>>> animations. It updates screen only when mouse is moved, or some slower
>>> > https://photos.app.goo.gl/QHgKCeeP2bnQGESu5
>>> That's really weird. I see two systems running at the same time there -
>>> same image? Different VM?
>> Yeah, those are running the same image on different VMs.
>>> > I suspect that there might have been some options I needed to pass in
>>> to specify some timers? Can you think of other reasons why this might
>>> happen and where to look to fix it?
>>> I never had any timer related options to worry about, so it shouldn't be
>>> anything to do with that.
>>> What happens if you use the 'new' VM but don't use the compositor/input
>>> thing? IIRC I had terrible problems caused by that ibus program and we had
>>> to make sure it didn't get into the Raspbian release.
>> I'll check it out. I wasn't expecting this kind of problem and did not
>> fully test things out.
> Not having compositioninput does not fix the problem. With a non-scratch
> image and I run BouncingAtomsMorph, the screen update on my VM is one frame
> per second unless I move the mouse pointer.
> Which function to obtain the current time to tell the VM to run the next
> event loop? I can check if it is called.
One datapoint is that making the argument for aioSleepForUsecs
in display_ioRelinquishProcessorForMicroseconds() to be always zero:
static sqInt display_ioRelinquishProcessorForMicroseconds(sqInt
aioSleepForUsecs(handleEvents() ? 0 : 0);
// aioSleepForUsecs(handleEvents() ? 0 : 1000);
makes it run smoothly. So the return value from handleEvents() would have
to make sense.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Vm-dev