Pad selectors(or "radio" selectors)

[kortezzzz]

@kortezzzz...
If you can isolate the issue with Trog's radio, stick it in example fsm and up it to General section,
I'm sure the gurus can probably sort it out if Trog's busy/not around...

Just saw this note...
Well I'm fine with it. The plugin that uses this module has been released already, but must say I had to make lot's of tweaks to match it to my design.

You can see the results in the product page at my site:

http://www.tornsub.com/ProductDetails.aspx?pid=4

[billv]

I just had a weird afternoon after work, everything i tried in FS worked..really strange..
Here's the latest...
@Walter..
Your "Left mouse delete" is there...
In properties there is a question.."Left mouse delete as well?"... answer no or yes..

The accurate mouse capture is installed.
(If you have used the Painting canvas, you might have noticed the delivery of the
mouse capture is not real fast...this slight delay is even more noticeable with this
module when large grids are used) ..Still works..just a bit sluggish...

I wasn't sure if Walter wanted Gradient for the Foreground or the background, so..
Did the sensible thing...
For the foreground and the background you can select either..
Brush,Gradient, HatchBrush or Texture Brush...
Extra colors and controls for Hatch and Gradient..
The Texture brushs have an array of 30 textures included...(small bitmaps)...
....the module goes in/out of toolbox pretty smooth...

Bear in mind there's a lot of stuff in properties now...I didn't set up a "purging" routine...
So when you export...delete what you don't need to optimize, if you feel the need......

Known issues: dragging on borders turning on both sides.... and Preset String still being used..

Grid_BV_RowsandColums_v4.fsm

(940.49 KiB) Downloaded 1160 times

[tulamide]

and Preset String still being used..

What exactly are you trying to store using the preset string? I could think of a few ways, depending on your answer. I started the fsm, but, and I hope you forgive me saying that, it is a bit of a mess. It would take me some time figuring everything out (no indenting also isn't helping). It's easier if you just describe it in detail.

Btw., I'm working on something quite similar. But it isn't exactly this, it's more like the pads of a drum synth in functionality. I will publish it when done, maybe there's something in it that you can use for your project, too.

[billv]

What exactly are you trying to store using the preset string

ATM I'm saving the 'selection' array via preset string... works fine...
But as pointed out earlier, arrays larger than 250 chr will have issues.....
So the VST parameter preset needs to replace the Preset String Prim...
I havn't got a result yet with that modification....that's all...

Ps:
Thanks for the tip that the fsm is a mess and hard to read/confusing....
Heard lots of similar complaint before...

[tulamide]

Heard lots of similar complaint before...Will stop uploading.

That would be a shame. I mean, those who are using your module are only interested in that it is working, and won't need to take a closer look.

I just offered my help, so I'm quite confused from your answer. It reads as if you're angry about my offer. I was thinking about bitmasking the state of the pads. That way, 1024 pad-states would fit into one 128-byte string, which is easily storable as a preset string. But if you want to do it on your own, that's fine. A simple "Thanks for the offer, but I prefer to figure it out on my own" would have been sufficient then.

[billv]

It reads as if you're angry about my offer

No not at all...that's why i went back and deleted the "Will stop uploading" comment.
Was written in haste, not explained well....so easily taken the wrong way....
Thing is, I actually thought i did good job making the code readable.
I don't know, i seem to writing ruby in "another language", so to speak.
This is magnified even more when i see other peoples code...and it looks nothing like mine..
So I'm thinking, should such code be in "examples"..will it lead other 'noobs' into bad
practices, and bad coding habits....makes sense....examples should be examples,
not confusing noob experiments like mine that always seem to be faulty.

[tulamide]

I don't know, i seem to writing ruby in "another language", so to speak.
This is magnified even more when i see other peoples code...and it looks nothing like mine..
So I'm thinking, should such code be in "examples"..will it lead other 'noobs' into bad
practices, and bad coding habits....makes sense....examples should be examples,
not confusing noob experiments like mine that always seem to be faulty.

Oh, then I'm very sorry to have hit a trigger. It wasn't on purpose. On the contrary, I think that we all can't learn if everything is right from the beginning. It's totally normal to have issues in posted examples. We all have them (just remember my first posted example here ).

Regarding "it looks nothing like mine". That's not true. It is just a bit syntactic structure and one or the other comment, that's missing. Nothing spectacular. But if you haven't written the code, you start at zero and try to both, read the code and understand the developer's thoughts. And that can be tough sometimes. For example, when identation is missing.

It would be a shame to not upload anymore. You always come up with awesome ideas (like your canvas).

[billv]

Oh, then I'm very sorry to have hit a trigger. It wasn't on purpose

All good mate...I'm just a bit 'over-sensitive' ATM, and not having a good relationship
with FS. A few weeks back, I went through "nil error" HELL for about 3 days, and it really done
my head in .

It's totally normal to have issues in posted examples

Yeh your right in a way...

bitmasking the state of the pads. That way, 1024 pad-states would fit into one 128-byte string

Not ignoring this....just too hard for to grasp ATM...

[Walter Sommerfeld]

Wow billv - what a nice 2nd sunday in advent gift!

@Walter..
Your "Left mouse delete" is there...
In properties there is a question.."Left mouse delete as well?"... answer no or yes..

I know i`m sometimes a pain in the a.. but i have 2 ask here 4 a favour from u - again :
Delete while dragging just like selecting...!

I wasn't sure if Walter wanted Gradient for the Foreground or the background, so..
Did the sensible thing...
For the foreground and the background you can select either..
Brush,Gradient, HatchBrush or Texture Brush...
Extra colors and controls for Hatch and Gradient..
The Texture brushs have an array of 30 textures included...(small bitmaps)...
....the module goes in/out of toolbox pretty smooth...

You've outdone yourself.
I need(ed) this 4 emulating a light bulb as a source behind the pads/buttons...

Known issues: dragging on borders turning on both sides...

I hope u can manage this 2...

cheers,
Walter

P.S.: I miss a reset/init after changing the rows and column size like 4x4... even after turn ruby on/off i have to set/reset all pads 2 get a proper output...
hint: implement the @grid.size into the Rand Array...

[billv]

I know i`m sometimes a pain in the a.. but i have 2 ask here 4 a favour from u - again :
Delete while dragging just like selecting...!

No worries Walter....I'm happy to try any mod...just another excuse to learn more...
Do you want to do it all with just the left mouse, is that right?
Sounds like you want a draw behaviour like Myco did with my Matrix trigger back in SM..
If the first square you click is off, click or drag will turn all selection(s) on...
If the first square you click is on, click or drag will turn all selection(s) off...
I'm not familiar with Win 8 touch stuff....do you need right mouse stuff removed..?

I need(ed) this 4 emulating a light bulb as a source behind the pads/buttons..

Great. Glad that worked out.
I'm seeing a problem with the Texture setting in the b/g squares...mouse drawing slows right down..

Known issues: dragging on borders turning on both sides...
I hope u can manage this 2...

Yeh, this is annoying, and really needs to fixed, but might take me a while...
I've used a Logical "and" for the first time and its confusing me a bit...
Plan B is to up a small drawing example to general section, and get trained on how do
this inner/outer technique thing...work it out eventually...

P.S.: I miss a reset/init after changing the rows and column size like 4x4... even after turn ruby on/off i have to set/reset all pads 2 get a proper output...
hint: implement the @grid.size into the Rand Array...

Yes.. your right...was easy fix...in meantime, you can drop this straight in..
In def event, there a code block that starts with "if i == 7 or i == 13 then "
Replace the whole block with this'

Code: Select all

  if i == 7 or i == 13 then 
    @sizex = 2 if @sizex < 2
    @sizey = 2 if @sizey < 2
    nilerrors
    @draw=[]
    @posarray=[]
    @posarrayaltvalue=[]
    @boolarray=Array.new(@sizex*@sizey){|x|x = false}
    @valuearray=[]
    output 0,nil
    output 1,[]
    output 3, @posarray
    output 4,@boolarray
    output 5, @posarrayaltvalue
    redraw 
  end

EDIT:
Also the mouse drag delete is wrong with the accurate mouse drag code...
Its not deleting each selection in order when you drag, it's just wiping the whole array..
EDIT2:
The grid size parameter is there inside the rand array...

Code: Select all

def event i,v
@a = Array.new(16) { |x| x = (rand(0..127)) }
output 0,@a
watch @a
end

127 is used as the grid size here...