Is there a know issue with mBlock (2.2.1) on OS X randomly/repeatedly failing to respond … where a Force Quit is required to terminate the program? I experience this quite often. I’m currently running OS X 10.9.5.
Unless I am missing something or doing something wrong, this appears to be a serious stability issue to me and I’m about ready to set mBlock aside until addressed.
Comments?
One (perhaps significant) thing I should have mentioned in my initial post is that I am communicating between mBlock and an mBot over the 2.4GHz link. The mBlock instability I note could possibly be due to occurrences or sequences related to the link.
For instance, if I turn off power to the mBot while a program is running, this seems to reliably crash mBlock running on my desktop. I will see if there are other events I can create or observe that also cause mBlock to stop responding, thereby requiring a Force Quit to terminate the program.
@larry, you can refer here: http://forum.makeblock.cc/t/faqs-how-to-install-makeblock-usb-driver-in-my-mac/2020
Thank you for your response @Pioneer. The application (mBlock) program crashing however does not seem like a USB related problem to me. I have previously installed the mBot USB drivers, and have been successful communicating with the mBot both over cable and 2.4GHz link. I do not think there is a USB problem.
As I mentioned in my last post, mBlock can be made to crash all the time if power is interrupted to the mBot while a program is operating, and mBot is operating wirelessly at 2.4GHz. This is something I think you should easily be able to repeat and confirm. I believe it is a common situation where users/students would accidentally turn off mBot power without first stopping a program. Once mBlock stops responding, a Force Quit is the only way to terminate the program.
(I did however reinstall the CH340/341 mBot drivers per the link you sent … there is no change).
@larry, we have reproduced your problem, our testers told mBlock would go crash mostly because mBot is power off but if still under communication, however, it shouldnt happen like that. We would push our developers to fix this bug in the next version, thanks again for your feedback!