Questions about the target checkmarks

[Softcore]

Excuse me if this is anywhere discussed in detail and I didnt find it!

In my effort to deeply understand the vast capabilities of Lemur, here are my questions:



In the example situation above I understand that:

The disabled "x" means that no message is sent to the OSC and Midi targets. The disabled "out" is a user defined variable so I figure, this also disables the OSC and Midi targets for this. As I understand, disabling "out" doesnt disable the "selecttab" action I have specified in the user defined variable "out".


Question 1: Does that mean that Lemur also doesnt "monitor" the incoming messages for said parameters? In other words, is it a good practise to disable anything in my project which serves as a control of other elements inside the project in order to have low usage of RAM;

Question 2: Since I wont be using any Midi/OSC targets to select the tab, would it be best if I had created a multiline script and not an "expression" for selecting the tab via the value "x" of the button?

Question 3: What exactly the checkmark on the name of the button "Custombutton8" disables? At first I thought it would disable all the elements down the hierarchy but thats not the case - as I tested if the script "action()" works with "CustomButton8" disabled and it works. So what does it really do?

Thanks in advance!

[Softcore]

Double checked the manual, still cant really understand what the checkmark next to an object's name enables/disables....

Anyone?

[Macciza]

Hi
Section 5.5 in the manual . ..
Primarily they are for the midi/OSC mapping of variables or objects, but also execution of scripts etc . . .
I would have to check for all it's intricacies . .

1. I think if it has midi mapping set it responds to input and the checkmark enables/disables output.
Your local control elements should not have any midi mappings set so not an issue.

2. Much of a muchness I think. Set the MIDI to none and all is good, if you decide you want MIDI input control then map it, if you decide you want output do it . .

3. Disables the variables & expressions MIDI output , set in the midi mapping pane, down the hierarchy.
No it does not seem to disable scripts within an objects, that has to be done individually

Not sure of the exact rationale behind all of its operation, it probably goes back to the original hardware . . .

Hope that helps

MM

[Softcore]

Ok, thanks for the insights!