Editing Visual Metronome - principle problems

[amt8probs]

Hello.

First my goal:
I downloaded the patch "Visual Metronome" from here (http://www.maxforlive.com/library/device.php?id=566) which really get close to what I want. Now I wanted to change the "quantization" of the patch so the blocks won't switch every 1/4 note to the next but only every bar so it would visualize me a 4 bar quantization.

What I have tried:
Editing the patch brought me to some unexpected difficulties which I wasn't able to resolve for myself with the helpfiles and my basic understanding of m4l. The patch which contains the calculations and optics of the metronome is inside a "p" object. So when I de-encapsulate it and encapsulate it again I destroyed the layout of the opening window of the whole patch - even when nothing else changed. I don't understand why. Doubleclicking the object (like the helpfile of the patch object suggests) won't open the subpatch - it sets the cursor inside the object. So I found the de-encapsulate command in the menu. Is this the right action? Can someone guide me to the right helpfiles or turtorials to understand whats going on? I am relatively new to m4l but have basic knowledge of max itself so sorry if the question is to simple.

My current interesting workaround:
I have an apc20 to which I send notes so It actually shows me with the scene select buttons the visual metronome. Kind of interesting solution the other way around.

Best greetings.
Bruno

[amt8probs]

Okay. After looking at other simple patches working with an separate window I realised the principle problem I had: When you open up the editor and then left the presentation mode you are automatically in the edit mode. So you can't just open a sub-patch. You have to left the edit mode so the separate window with the included sub-patch opens up. Really simple but I didn't get it in the first line.
After tweaking the appearance so it fits my liveset I now try to make the window sticky (always in foreground)... but I will solve that too.

[amt8probs]

So after some trial and error I found the solution for keeping the window in the foreground:
You have to place a "thispatcher" module in the subpatch and then deliver parallel to the open command to the pcontrol the argument "window flags float" to the p module. I read in the max forum of "topmost 0" but that didn't worked.
Have a nice evening.