General
Multiball's Grid, button on/off ?
Started by Liko on .
Sign in or create an account to join the conversation.
Hi there, its my first post...
And i would like to know if its posible to make a button to activate or desacivate the grid option in a multiball...
Thank you!!!!!
And i would like to know if its posible to make a button to activate or desacivate the grid option in a multiball...
Thank you!!!!!
A button activates the MultiBall grid. Two knobs adjust the number of steps for x and y axises.
mball-grid-settings.jzml
mball-grid-settings.jzml
Alternate version with one knob for the steps - which keeps them always equal between x and y and produces a "squares" matrix.
mball-grid-settings-sq.jzml
mball-grid-settings-sq.jzml
This was what i was looking for, really apreciate it!
P.D. do yo know how can i iniciate in learning more about creating skins?
thanks again..
P.D. do yo know how can i iniciate in learning more about creating skins?
thanks again..
If you are asking about custom skins, this is currently not possible. I was initially excited with the "skins" implementation thinking this would be the start of a system to create our own skins but ermmmmm....given the current rate of updates - fixes, dont hold your breath!
No, sorry... I mean to create "proyects" let me explain... My english it's horrible... Excuse me for that! Well i mean like with the grid option. You have writed : setattrribute(multiball, 'grid' , x ) ;
And this its what makes the button activate the grid in the multi ball? Well i want to learn how and why this works like this and i whant to learn this type of language... And all it can do in the lemur editor... Where i can find tuttoriarls for beguinners like me...
Thanks.
And this its what makes the button activate the grid in the multi ball? Well i want to learn how and why this works like this and i whant to learn this type of language... And all it can do in the lemur editor... Where i can find tuttoriarls for beguinners like me...
Thanks.
Oh i get ya now!
First of all read the manual of lemur - this covers ALL the basics.
The first and foremost beginner tip I can give is that all objects "operational" values are x,y,z (some dont feature all of those three). Knobs and sliders have x values that range from 0 to 1. Switches and pads x values are 0 when off, 1 when on. You can control ANY object by simply referencing these x values.
For example Knob.x=0.5;
sets a knob to its halfway value
Switch.x=1;
sets a switch on
Lastly, look up the attributes of each object - there is a reference at the end of the manual. Then you simply reference it in your scripts by using the
setattribute(object, 'name of attribute', value)
For oor example above the way it works is quite simple, x is 0 when the switch is off, x is 1 when the switch is on. So, the grid attribute is 0 when the switch is off and is 1 when the switch is on. Generally speaking, whenever a on-off state is required, 0 is off, 1 is on (boolean).
Again, all the basics are covered in the manual and shoulod be more than enough to make simple operations - for the rest, the user library is your source of coding, programming and inspiration!
First of all read the manual of lemur - this covers ALL the basics.
The first and foremost beginner tip I can give is that all objects "operational" values are x,y,z (some dont feature all of those three). Knobs and sliders have x values that range from 0 to 1. Switches and pads x values are 0 when off, 1 when on. You can control ANY object by simply referencing these x values.
For example Knob.x=0.5;
sets a knob to its halfway value
Switch.x=1;
sets a switch on
Lastly, look up the attributes of each object - there is a reference at the end of the manual. Then you simply reference it in your scripts by using the
setattribute(object, 'name of attribute', value)
For oor example above the way it works is quite simple, x is 0 when the switch is off, x is 1 when the switch is on. So, the grid attribute is 0 when the switch is off and is 1 when the switch is on. Generally speaking, whenever a on-off state is required, 0 is off, 1 is on (boolean).
Again, all the basics are covered in the manual and shoulod be more than enough to make simple operations - for the rest, the user library is your source of coding, programming and inspiration!
Subject: Custom SkinsHello, Has anybody heard about custom skins.Softcore wrote:If you are asking about custom skins, this is currently not possible. I was initially excited with the "skins" implementation thinking this would be the start of a system to create our own skins but ermmmmm....given the current rate of updates - fixes, dont hold your breath!
I have noticed that if you alter the skins within the lemur application the alterations appear on the editor but, not in the lemur when loaded onto the iPad, is there a way of getting into the skins on the i pad?
It makes perfect sense that in order for custom skins to appear inside the iPad there should be some sort of function-operation to upload the altered image files - skins to the iPad in the first place. Without having any "insider" info, I suspect this will also be considered at some point by the developers but this is ONLY a personal speculation.
Hope they do, i designed a few modules and they are great fun.
Only had this app a day now and i really enjoy it, i also own a lemur and am impressed with how large the interfaces can be on the IPad (the lemur's memory is much smaller).
Both devices play extremely well with each other, i only wish that the instruction manual had been re done or just much more technical info added but, there is a new community of people to ask advice from.
Only had this app a day now and i really enjoy it, i also own a lemur and am impressed with how large the interfaces can be on the IPad (the lemur's memory is much smaller).
Both devices play extremely well with each other, i only wish that the instruction manual had been re done or just much more technical info added but, there is a new community of people to ask advice from.