Hi, is it really required that you let the mouse and keyboard accessible? I mean all would be easier if you only provided kinda midi interface to the public.
Antoine Rousseau http://www.metalu.net http://metalu.net __ http://www.metaluachahuter.com/ http://www.metaluachahuter.com/compagnies/al1-ant1/
2017-09-12 14:54 GMT+02:00 IOhannes m zmoelnig zmoelnig@iem.at:
On 2017-09-12 14:25, Jean-Marie Adrien wrote:
Hello I will make an installation in a public space soon where the machine
(mac) will be somehow accessible :
for responsibility and privacy reasons, i’d like to make it impossible
to manipulate the patches
(first time i encounter this issue in my long usage of pd…) Is there a way to lock everything ? compile or whatever ? i mean once a patch is running, the mac is basically accessible, no ? (session opened, mouse and keyboard operable, not talking about ethernet) What i have been doing until now is run patches in public spaces tor
theaters just as at home and that was fine, but won’t be ok this time
nothing very sophisticated, but my kiosk-plugin might be of help: https://git.iem.at/pd-gui/kiosk-plugin
it basically lets you disable menus, shortcuts, puts a patch to full-screen mode,...
i only ever tested it with linux, YMV on other systems.
also, it only fixes whatever an application can fix on its own. e.g. low-level keyboard shortcuts, that the application doesn't even see, e.g. [SysRq]+BUSIER) can't be intercepted.
fgmasdr IOhannes
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/ listinfo/pd-list