Selector

[Acrobat]

Try this:

Grab a selector and feed it with some float inputs BEFORE adding the Integer source.
Now adding the source changes the inputs and the ouput to INTEGER regardless they're floats. These may cancel the output to other parts of the schematic.

Happens also with V (view) and S (string) inputs.

[malc]

What do you mean by the "integer source", are you referring to the Index input? I don't get any problems here but maybe I'm not doing it right.

I add a Selector, attach some Float components to the inputs and the type of the selector switches to Float. I then tried connecting an Int component to the Index input (the 1st) and all was ok. I attached it to the template input (the last) and all was ok. Also ok attaching an Int to the output.

Should I be doing something different?

[Acrobat]

What do you mean by the "integer source", are you referring to the Index input? I don't get any problems here but maybe I'm not doing it right.

I add a Selector, attach some Float components to the inputs and the type of the selector switches to Float. I then tried connecting an Int component to the Index input (the 1st) and all was ok. I attached it to the template input (the last) and all was ok. Also ok attaching an Int to the output.

Should I be doing something different?

Yes, Integer source I meant Index, yes.

mmh.. well maybe you didn't connect the output to anything before connecting the index, I think the bug will not show in that case.

When the last thing you do is connecting the index, the bug appears. I'll try to take a snapshot of it, I'm sure I can reproduce since it happened to me many times..

[Acrobat]

Here is a screenshot, right after connecting the index: the view links changed to "I"
with no apparent reason ....



Nobody ever encountered that?

[aliasant]

Here is a screenshot, right after connecting the index: the view links changed to "I"
with no apparent reason ....



Nobody ever encountered that?

Yes. That happens to me too.
But if your control signal is a boolean this wont happen.

[Acrobat]

that appeared in 1.1 along with some other little glitches...

[Neptune]

that appeared in 1.1 along with some other little glitches...

Recognized it some weeks ago in 1.05 too. But it is hard to reconstruct.
It happened to me when i copied and pasted an selector from my project. When i changed the connector type (e.g. from stream to midi) the whole selector changed to the prior connector type (stream) when adding some midi inputs.

[Acrobat]

that appeared in 1.1 along with some other little glitches...

Recognized it some weeks ago in 1.05 too. But it is hard to reconstruct.
It happened to me when i copied and pasted an selector from my project. When i changed the connector type (e.g. from stream to midi) the whole selector changed to the prior connector type (stream) when adding some midi inputs.

yeah it's scrambled, in some way, seems to have a memory by itself...
I just found a situation were it changed to Integer from float, I didn't noticed since the're both the same color so the phase of some oscillators were fed with wrong values, not 0.25 and 0.75 but 0 and 1 for approximation - urgh - very tricky....

Don't fear it will change someday in the future, no, it will never happen without user intervention, WYSIWYG, just people my advice is: take care when connecting..