DSP Robotics Support

I tried to take the drop-down selector modules and make a set of them with identical options that wouldn't allow more than one of them to have the same option selected. You can see my attempt in the schematic.

What should happen is if you select a value that's already selected in one of the other selectors, the current one changes to item 0 ("None") instead. But my attempt doesn't update the output value correctly.

The triggers/values seem to be getting caught up inside the "preset" module. I don't know why. You can see the correct value going into it but the previous value is being held and output.

If anyone could help me out with how to fix this or a better way to do it, that would be awesome.

Also a question: when a modules link nodes have shadows flash underneath them, does that indicate something? Perhaps an error of some sort? Or is that some kind of visual glitch?

Much thanks.

Here's a quick fix, just put a condition on the output.

Hope it helps

EDIT
an even simpler solution


Though both suffer from the same odd behaviour where if you select say item 3 in slot 1 and try to select the same in slot 2 it displays none and outputs 0, so far so good
BUT if you try the same again slot 2 selects item 3 and slot 1 is turned off

I'm sure there's a simple solution and will give it a try tomorrow (well today but after I've had some sleep, which is tomorrow for me even though its still today, if you see what I mean, Neeeeeed sleeeep)

i did some similar things a while ago,

here is one which deletes already used items from the list in the other selectors:
viewtopic.php?f=2&t=1335&start=10

and her is one which changes the 'old' item to noFX when you choose the same item on another selector:
viewtopic.php?f=3&t=1497

Xtinct wrote:Here's a quick fix, just put a condition on the output.

Wonderful. Thank you!! Not only would I not have thought of that, I'm not really sure why that works.

Though both suffer from the same odd behaviour where if you select say item 3 in slot 1 and try to select the same in slot 2 it displays none and outputs 0, so far so good
BUT if you try the same again slot 2 selects item 3 and slot 1 is turned off

Indeed. Maybe we can call that a feature... if the user is that persistent, we're just giving them what they want.

Nubeat7 wrote:here is one which deletes already used items from the list in the other selectors:
viewtopic.php?f=2&t=1335&start=10

That's awesome. I considered trying that, but decided it would be much too complicated. I'm sure Ruby helps a lot there. One thing about that that would drive me crazy though is the way the drop list reorders itself. I need consistency there.

Really appreciate it though guys.

Xtinct wrote:
Though both suffer from the same odd behaviour where if you select say item 3 in slot 1 and try to select the same in slot 2 it displays none and outputs 0, so far so good
BUT if you try the same again slot 2 selects item 3 and slot 1 is turned off

not only this, if you now set slot 1 to item 3 slot 2 and slot 1 are set to item 3!...

How confusing. :S

So... I guess the booleans have to be reset or something since the checks only send triggers when it's set to true. If they're already true it won't send a new trigger.

Perfect Human Interface wrote:So... I guess the booleans have to be reset or something since the checks only send triggers when it's set to true. If they're already true it won't send a new trigger.

If that's really the only issue you might come away with these 2 little modules. Just like bool2true/bool2false they send out a trigger, but they send it whenever they are asked, not just on change.

Perfect Human Interface wrote:I need consistency there.

yes the schematics above are pretty old and unflexible...

its better to use ruby droplist and implement a small methode which checks if a item is already used and outputs something specific if true (zero for example)

i did a fast version of this idea, it has the advantage that you can easily add as much selectors you want..

tulamide wrote:If that's really the only issue you might come away with these 2 little modules.

Indeed tulamide, that's all it took!

Here's the current (hopefully fully fixed & working) version if anyone wants it.

I'm glad it helped. If only my own current issue could be solved that easy