a couple of ideas about data components

laserbeak43 · 17 Jan 2005

err my brain swole and my right eyball exploaded.

jorge · 17 Jan 2005

lalo wrote: 1. having a min and max value for integer/float data components

min and max is already possible with the min and max component. The whole philosophy of SM is to have very low-level primitives that accept values as input connectors. The idea is to wrap those primitives around prepared modules with data components ready for easy editing, the inside of the prepared module works in a similar way to a properties dialog box but in a much more flexible way. I suggest you create a module with a schematic for setting max and min value. If you want I can post a schematic here to show you how to do that. Drag your new module to the toolbox and use it instead of a float/int data. If you want to see the value in the module's GUI, that's possible too. If you dont like my suggestion please let me know.

jorge · 17 Jan 2005

lalo wrote: 2. for the float having a resolution setting so you can choose how many decimal you like to have (i.e. 3 will be 0.000 format, 1 is 0.0 etc...)

I think that should be done with a separate primitive with a float input connector, a float output connector and an int input to define the number of decimals to use. Can you tell me an example of a situation when that would be useful?

lalo wrote: 3. A kind of constant button (float integer and string) in wich you write a value and when you click on it the values is sent to the outlet...this is very handy when you want to quickly try different values for something.

I think that's already possible using the Float Sample&Hold and the Float Switch primitives, if you want more details let me know. Once again we should follow the philosophy of creating prepared modules rather than doing everything starting with the low-level primitives

lalo wrote: point 1 and 2 could be a kind of right click contest menu with the relevant properties

right-click contest menu to change min, max, range etc...? where have I seen that before? actually, that's not a bad idea, but I think it should be flexible like it was in the old version of SM so that you can create your own properties dialog box and trigger it from a custom button in the Action panel.

lalo wrote: in future even 'list objects' and operators to deal with would be a nice idea

that has already been planned, it already exists with the Graph data which is actually a FloatArray. The Graph connector is going to change to a new type of FloatArray wich is like the float connector but with a green dash circle around it, the same will happen for StringArray and IntArray.

lalo · 7 Feb 2005

hi jorge ! another little idea... have a 'view' inlet in data components... so i can test vst/i without messing with GUI stuff 😀 this can be a good approach even before the 'export vst/i without GUI' function thanx lalo