Exclusive Selector- Halp?

[Perfect Human Interface]

Indeed, I may just adopt that working framework, if Nubeat doesn't mind. I just figured that what I already had was going to be fine after the proposed fixes. In general I'm kind of pissed off at the preset parameter thinger for working like garbage right now, even if it is my fault. I don't even know what the hell was happening with the edit boxes I was working on earlier, where it only started working correctly after setting "auto" to false.

[tulamide]

Wow I can't believe this thread is still going, I was sure it would stop after Nubeat7's first example which ticked all the boxes.

Why do you assume that? Sometimes people need more than a premade solution, since they want to learn. It's easier to learn when keeping on working on their own schematics. A full featured solution of another one can be very confusing to read.

There might be a majority of people who just want to be fed with solutions, and that's ok. But asking for help on your own schematics and working on it until it's done, especially to learn from it, that's also ok.

[Perfect Human Interface]

One thing is for sure... I would never get anywhere with anything in Flowstone if it weren't for the community here.

[Xtinct]

Wow I can't believe this thread is still going, I was sure it would stop after Nubeat7's first example which ticked all the boxes.

Why do you assume that? Sometimes people need more than a premade solution, since they want to learn. It's easier to learn when keeping on working on their own schematics. A full featured solution of another one can be very confusing to read.

Which is exactly why I said I'd try to recreate it in green as I and a few others find it easier to follow.
I just thought the idea of not only not being able to select a previously selected item but the fact that it removed that option was kind of fool proof for any end users who might think there was a bug because when they chose an option that was already selected it kept returning a none status, much better to remove the option and save confusion. So it was the solution I thought would stop not the schematics on how to reach it.

[Perfect Human Interface]

Nah, I already mentioned the problem I have with it (it reorders the drop-down items). I can expect me users to not be quite that dumb. It's a perk of working with something that requires a degree of education in the first place.

[RJHollins]

One thing is for sure... I would never get anywhere with anything in Flowstone if it weren't for the community here.

Absolutely true for me too !

What I also tried to learn from, is the 'logic' that You programmers' use to solve ... let alone the Prims and Code involved. That is why I try to follow threads I'm not currently interested in ... or those way over my head. I still look to learn what I can.

I've said it before, and again ... Thanks to everyone's forum contributions. This is my schooling

[Xtinct]

I can expect me users to not be quite that dumb. It's a perk of working with something that requires a degree of education in the first place.

But dumb enough to select the same thing twice or you would not need an exclusive selector.

[tulamide]

I just thought the idea of not only not being able to select a previously selected item but the fact that it removed that option was kind of fool proof for any end users who might think there was a bug because when they chose an option that was already selected it kept returning a none status, much better to remove the option and save confusion. So it was the solution I thought would stop not the schematics on how to reach it.

I agree with you on this one. I also would prefer to offer the idea of removing options depending on previous selections. It makes strictly clear that there is only one selection per item possible.
But I'm also willing to agree that a simpler approach might be better sometimes, to get it right in a reasonable amount of time or for learning purposes.

Btw: What you said about green, count me in. The visual scripting is what most people brought to Flowstone. It is very unsettling to see ruby in the stock modules instead of green, for someone who is learning the "place and connect"-concept of green. Yes, ruby can be so much more effective, but it's also far away from the visual scripting aspect.

One thing is for sure... I would never get anywhere with anything in Flowstone if it weren't for the community here.

Absolutely true for me too !

What I also tried to learn from, is the 'logic' that You programmers' use to solve ... let alone the Prims and Code involved. That is why I try to follow threads I'm not currently interested in ... or those way over my head. I still look to learn what I can.

I've said it before, and again ... Thanks to everyone's forum contributions. This is my schooling

The same is true for me, too! Everyone who spends some of his/her time to help others makes this community a valuable place. It also encourages to do the same. Which is why I started to at least contribute modules after I was getting help. To give something back.

[Nubeat7]

i think in this case it really is easier to do it in ruby, the big advantage is that it enables you to check if any other item is used before you send the selection out of the module, so the only thing you have to do is to write this little methode 'check_if_used' and use it just before you send the selection to the output, the rest is just the normal ruby droplist from the userguide (208) while in green its a pain to follow all the triggers which are happening and taking care that it works also right with the presets and updating the label, for me is much more difficult to follow all this different trigger targets then having one simple methode in ruby and having a module without lots of triggers and connections to get everything updated properly, i needed good 2 weeks to get the green version work and this only with triggerdelays which i really don't like

about user prove designs, at the end i dont really like both solutions, but if there is an item which you could choose, also if its locked, it should be in the list, sadly we have no way to mark any items in the droplist as locked (make brighter colo for the text or put a star in front...) which would be the best way because it tells the user it is here but you cannot choose it, finally i think its the best way when there happens nothing when the item you want to choose is already used or you can choose it always but it sets the selector which used it before to 'none' to give priority to the last selected, this really depends on the situation where it is used..

[RJHollins]

I have a project that could use an 'exclusive selector' function. So this is a great subject.

My program has 12 sub-modules that each send MIDI data out a specific MIDI Channel. I want the User to be able to select a Channel for each module any way they choose ... but never 2 modules using the same Channel.

The project is still evolving, so currently there is NO exclusive function happening ... but I've been trying to consider how to handle this. Not just code wise, but functionality wise from the User perspective.

I really like the idea of NuBeat's exclusive 'pool' selector. I aspire to that level, but am very far from that.

Like so many useful modules ... like the 'radio button' flurry we had before ... everyone has a different take and implementation that presents different ways to do things of similar function. I think this is fantastic and much appreciated. It seems to open/expand thinking, and can motivate to something in different directions.

What I describe might sound quite lame to those much more experienced/accomplished ... but if not for the SM/Flowstone concept, I doubt I'd be involved with any type of 'programming' at this stage of life. I'm an audio engineer by profession. Being able to make some application tools that help me do what I enjoy has been great ... frustrating at times, but I strangely enjoy

I hope we always see members continue to share their programming ideas and questions and knowledge. I hope to learn enough that I could even offer help in return.

Still glad we have a nice collection of GURUs here !


---- edit ----
Just saw NuBeat's post [above].

I think you expressed a really good, functional way of a [more] ideal working .... even if it is NOT possible.

I was thinking on how a selection might be 'greyed out' [signaling that it was already selected], and that it could be re-assigned in the current selection. But then we'd still need to trace down where the original assignment was, etc.
Just seemed having to go back and forth. In otherwords ... this is NOT as easy as it might seem

Guess it really depends on the application needs and layout. That's why I thought your 'pool' solution was still a viable solution. I think the pull-down menu also adds to the issue ... as handy as it is.