Mock App disconnects about bluedot HOT 6 CLOSED

Can you provide your script please.

from bluedot.

It's the first sample script from the recipes ( http://bluedot.readthedocs.io/en/latest/recipes.html#mock-app )

from bluedot import MockBlueDot

def say_hello():
print("Hello World")

bd = MockBlueDot()
bd.when_pressed = say_hello

bd.launch_mock_app()

from bluedot.

I see the problem.

I tested running from IDLE which keeps the application alive. If you run from the command prompt as soon as the mock app has finished launching the program ends which simulates the client disconnecting.

If you want to run it via the command prompt you will need to use pause() to keep your program alive.

from bluedot import MockBlueDot
from signal import pause

def say_hello():
    print("Hello World")

bd = MockBlueDot()
bd.when_pressed = say_hello

bd.launch_mock_app()

pause()

Ill update the docs.

Also as an aside, I would recommend running your programs using python 3, i.e.

python3 m.py

rather than:

python m.py

which runs as python 2.

from bluedot.

Fantastic! Works like a charm now! Great stuff, this. I really like it a lot, so much potential.

and btw: sorry for the strange font size above, I think I accidentally touched a button....

from bluedot.

Off-topic, but I think you'd like to know this. I installed everything (IDLE on Python3, Pygame, BlueDot etc.) on my laptop (Intel i5, 6 GB running Linux Mint) and the Mock App runs well, but takes almost 98% CPU... My laptop overheated and shut down.

?

from bluedot.

Interesting. pygame must be doing something different with events. The Pi seems to wait until events occur rather than looping.

I have updated the mock blue app (v 0.1.2) to implement a clock, hopefully that will make a difference, its a better implementation.

I have also updated the docs re the original issue.

from bluedot.