Has anybody used kiosk-plugin (via deken) on a raspberry pi?
I downloaded and tested on osx and it works great, but when I try on the raspberry pi, the options I tried (disabling menus and making full-screen), didn't work. The console seems to think the plugin is loading properly. Is there a known issue?

pd version 0.51.4,
rpi os bullseye

Exactly the same issue here, looking for any kind of alternative or fix to this.

@EwanBristow Not all wm (window manager) attributes are supported in Linux.... some window managers support more than others......
You will be able to modify the plugin.... it is just a text file.... if you can find a workaround...... https://wiki.tcl-lang.org/page/wm+attributes
David.

@whale-av I don't think kiosk-plugin uses wm attributes other than full screen and the title, the rest is pure tcl/tk? Or am I missing something? I am just starting to not be completely confused by tcl/tk so am still confused fairly often. I tested kiosk-plugin on a few different wm all of the quirky nonstandard sort which often lack in the things it is generally assumed a wm will support, the only issues I had was in tiling wms full screen does not quite work but it often doesn't in tiling wms since they are doing their best to force everything into the tile.

@oid I understood (from the op) that it is the window control that is not working....full screen and removing the menu bar. I think that if the attribute control doesn't exist in their window manager then there is no way that they can address the issue, other than using a different window manager...... probably..!?
It's unusual that the window manager doesn't give fullscreen control though.

I had a good go at tcl/tk years ago, but you are way ahead of me.
David.

@whale-av But menubar would be gone, perhaps that part did work and he forgot to mention that? I think you would be hardpressed to find a wm which does not honor the full screen attribute these days other than some tiling wms. I did just remember wayland which debian seems to use by default but xwayland should properly handle the X stuff if I understand how it works correctly. This might be worth a bug report but I am not sure where that bug report should be made or how to figure that out.

Running a non-wayland wm might be an solution, but this might require switching to X as well or xwayland my handle it and solve the issue. I don't know wayland well enough to offer anything but guesses.

@whale-av
managed to fix it, i was attempting to use "startx /pd /mypdpatch.pd" and have kiosk do the full-screening for me. My mistake was not realising that the pd console was the one X was attaching itself to.
Silly issue on my part.
Appreciate the support none the less, perhaps @mbbaker has a different issue.