SBMastering wrote:Is this actually complicated or should I be able to do something like this after a week of using Synthmaker?
I would say that it is not a trivial problem - in the post where you found your example, there are hints at why this is so.
Trouble is that SM sees mouse-down, mouse-up, double etc. as discrete events - which it kind of has to to allow us maximum flexibility.
For double clicks, this can create problems, as the individual presses and releases of the buttons get registered in addition to the double click event - cruciallly, there will always be a mouse down event that happens at the same time as the double click. You can see this if you experiment with this example (hint: try holding the button for a moment on the 'downstrokes' to see exactly when the double event is sent)...
Depending on exactly how the schematic is arranged, and what order the 'Down' and 'Double' are connected to the Mouse Area, this can lead to contradictory messages clashing with each other inside the control - and hence, the final effect can appear unpredictable. In fact, in Xtinct's example it took me a while to even find where he had put the double-click - it is not inside the 'interaction' modules along with the other mouse handlers - and I guess he has done it that way precisely to keep the double as separate as possible, in order to overcome these 'clashes'.
So, don't be disheartened, this is one of the trickiest bits of SM to understand - even after many years using SM, I find myself having to resort to trial-and-error to fix these kind of problems. It is not helped by the poor manual - as you have found, only the primitives (blocks that you cannot go inside) are properly documented . Many of the modules (with 'inner workings') were not even created by the SM developers, and have been collected together from the contributions of users over the years.
To learn more, I would suggest that the only way is to start small - complex modules like the knobs and sliders, have so many zillions of links and modules within modules, that I doubt even the 'old timers' here could ever completely describe how every part works. Things like the little example I posted above will teach you much more - just like any scientist, you can add or change one small thing at a time, use readouts and trigger counters to look at what's happening, and then ask here on the forum any time you get a result that you don't understand.
I also recommend reading my (sadly still incomplete) 'Trigger Tutorials
' guide to how SM handles triggered data (green and yellow parts) - I think that this is the part of the official manual that is most lacking, and leads to the greatest confusion for beginners. It is far from comprehensive, but will hopefully will at least give an insight why an apparently simple bunch of connections can behave in ways that defy 'common-sense', and some ideas for what to look up when searching the forum posts.
And remember - all of us here learned the same way; from each others' examples and asking lots of 'dumb' questions. No-one is ever going to look down their noses at you for asking questions about the 'basics' - because we all had to do that when we were beginners.