Overview

[gsalaman]

(using issues as a messenger conduit)

Tuesday afternoon works for me...you said you were free starting at 1:15, right?

[jlefkoff]

I am free starting 1:40pm on Tuesday

[gsalaman]

Cool, I'll see ya then.

[gsalaman]

Thought more about the file path thing...I think instead of me passing full path (which is then not robust if we move the program around) I instead should tweak the "client" programs to be more resilient if a file doesn't exist.

Example: if we try and read the high score file, and it's not there, just init it with a bunch of zeros, rather than failing.

Side effect: this means that we'll have the high score files and config files stored in the directory of your launcher app, created by the launcher program. Is that cool with you?

[jlefkoff]

I think that is ok. I can make a subdirectory for highscores. Just make sure each program makes a uniquely named highscore file.

[gsalaman]

Created issue for this in mqtt_gamepad, and I'm planning on adding the "mqtt exit" command to both as well. My plan is to have both those implemented and tested this weekend; if you want to integrate on Monday afternoon, I'd be down...

...and if this works, I'll add the mechanism to the camera and audio visualizer apps.

[jlefkoff]

Sounds good! I am also working on a hotfix for the moment. I think I can give a .sh script full root all the time priveledges, and then call it from the non root python program. We'll see

[gsalaman]

Shutdown command implemented, unit tested and ready for integration on Monday. Simply broadcast a "shutdown" topic (message payload doesn't matter), and any apps that support this mechanism will gracefully stop.

Current apps on makerlabpi1 that support this functionality:

• The worm game: /home/pi/glenn/mqtt_gamepad/wormgame_mqtt.py
• The audio visualizer: /home/pi/glenn/audio_mqtt (need to run both mic_full.py and dual_display.py...start order shouldn't matter).

Both these are currently pointing at mqttbroker.