From the original SynthMaker forum (2004–2014), with its members’ names and dates.
Acrobat ·
A new control for you! Evolving my other Grid project came to this, a full customizable active matrix control. Just choose sizes and the number of rows and columns, the schematic will arrange a matrix: with the mouse you'll be able to choose one of the cells!
Cheers, Andrea 😀
DigitalWhiteByte ·
Thanks 😀
sunsynth ·
Another fine Modul to place into ur group! 🙂
Thanks Andrea!
tektoog ·
Pretty cool !!! and very handy.... for what ... I dunno yet...!!! Thanks Acrobat...
infuzion ·
Very cool!
Bug: I think the selected box display needs an Int S&H to prevent a flash of the incorrect value being displayed before the correct box is displayed. Seems to happen along the XY axis.
Suggestion: Some way for the grid to be rendered only 1 time; render in a separate module on load only then I think Draw to Bitmap?
Acrobat ·
thanks
Bug: I think the selected box display needs an Int S&H to prevent a flash of the incorrect value being displayed before the correct box is displayed. Seems to happen along the XY axis.
I m not sure I got what you mean, I'll check that anyway... I work on 1.1.1, maybe it happens only in 1.1.7?
Suggestion: Some way for the grid to be rendered only 1 time; render in a separate module on load only then I think Draw to Bitmap?
No, because my general philosophy about SM GUI examples is to remain totally in vector, so everyone can resize things to its taste and needs.
infuzion ·
Acrobat wrote: Bug: I think the selected box display needs an Int S&H to prevent a flash of the incorrect value being displayed before the correct box is displayed. Seems to happen along the XY axis.
I m not sure I got what you mean, I'll check that anyway... I work on 1.1.1, maybe it happens only in 1.1.7?
Maybe since triggers have changed. See attachment for demo (first module v02 before I fixed it). On LMDown you will see the wrong box rendered. This happens very fast in your version.
Acrobat wrote: Suggestion: Some way for the grid to be rendered only 1 time; render in a separate module on load only then I think Draw to Bitmap?
No, because my general philosophy about SM GUI examples is to remain totally in vector, so everyone can resize things to its taste and needs.
I'm not saying never render in vector, I'm saying render in vector only once on startup, not at every click. Read MyCo's OSMs: [old link]
New found bug: Mouse-selecting a box sends extra "0"-value triggers.
Acrobat ·
I'm not saying never render in vector, I'm saying render in vector only once on startup, not at every click.
Mmmh, that's a great trick but I think it follows kind of a selfish way instead of an interactive way of thinking. Bitmap rendering is not suitable for a module is supposed to be part of a bigger project, where floats related to this matrix can interact with other graphical elements.
Acrobat ·
All triggers problems you pointed me out are defiitely NOT present in 1.1.1! So as Damon Alban says in that song: "it's not my problem".
...I'll try to load your attachment in 1.1.1 and see what happens.... 😉
Acrobat ·
I've look over the bug you mentioned, infuzion, it seems the new version of SynthMaker has completely different way of using green triggers, that's the problem. The version you have arranged does not shows the dragging anymore, so the user has no feedback on the mouse movements and that's wrong. I don't know if you see the cell selection movement with the new 1.1.7 triggering method. That's confusing! 😕
infuzion ·
Acrobat wrote: I've look over the bug you mentioned, infuzion, it seems the new version of SynthMaker has completely different way of using green triggers, that's the problem. The version you have arranged does not shows the dragging anymore, so the user has no feedback on the mouse movements and that's wrong.
I think Malc told me that the S&H (in general) may be problematic due to there can only be 1 S&H in a code section. Any more will be messed up & not likely to trigger. Trick is some primitives my have a S&H hidden inside. I didn't think about testing for dragging, sorry!
Acrobat ·
infuzion wrote: Acrobat wrote: I've look over the bug you mentioned, infuzion, it seems the new version of SynthMaker has completely different way of using green triggers, that's the problem. The version you have arranged does not shows the dragging anymore, so the user has no feedback on the mouse movements and that's wrong.
I think Malc told me that the S&H (in general) may be problematic due to there can only be 1 S&H in a code section. Any more will be messed up & not likely to trigger. Trick is some primitives my have a S&H hidden inside. I didn't think about testing for dragging, sorry!
OK, well about the S&H that's incredibly limiting, don't you think so? I'm astonished about green flow problemsin 1.1.6-7 as it seems a step BACKWARD for SM. That makes me even more convinced to remain stuck at 1.1.1. But I'm loose contact with other developers and that's very bad. 😕
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker