Exclusive Selector- Halp?

[Perfect Human Interface]

but if there is an item which you could choose, also if its locked, it should be in the list

That's exactly what I was thinking. For me, reordering the list (which includes outright removing items) isn't acceptable. That's just far too annoying (and note my project has something like 16 items in the list!). Keeping the item in the list but disabling/locking it would be the ideal. But who's going to make that? I don't know how. So with that being the case... unless someone comes along with a brilliant execution they're willing to create and share with all of us, I'm willing to compromise with my original design.

And I would definitely prefer that the items switch to "none" instead of staying the same. I feel that in an interface, if the user tries to interact with something and *nothing* happens, that suggests "broken." By switching the selection to the "none" setting, that can in some way suggest to the user that their input was received but the setting was deemed invalid.

The feedback is all cool though!

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

It's managing consequence. If a user tries to do that, and it doesn't let them, they say "oh, I can't do that." If on the other hand they try it, and it blows up with some infinite signal, they say "what the %^&*!" Big difference there.

[Nubeat7]

Keeping the item in the list but disabling/locking it would be the ideal. But who's going to make that? I don't know how. So with that being the case... unless someone comes along with a brilliant execution they're willing to create and share with all of us, I'm willing to compromise with my original design.

And I would definitely prefer that the items switch to "none" instead of staying the same. I feel that in an interface, if the user tries to interact with something and *nothing* happens, that suggests "broken." By switching the selection to the "none" setting, that can in some way suggest to the user that their input was received but the setting was deemed invalid.

i'm afraid if you want to mark items in the droplist as locked you need to create one by yourself instead of using the windows one,it would also have the advantage to design it by yourself instead of having this boring gray windows one

about the thing 'nothing' or 'none' when item is used you are right about that the user could assume its not working but for me it would be annoying when it is set to none only because the one i wanted is not avaliable, maybe you could leave it on the old item and generate a infobox which tells the user that the item is already in use? shouldn't be to hard to integrate..

[Perfect Human Interface]

I'm afraid there is an issue of the fact that the projects I'm working on are already quite ambitious. I can't really afford to make a full project out of a drop-down menu right now, unfortunately. I just need something that gets the job done.

[Nubeat7]

maybe you could leave it on the old item and generate a infobox which tells the user that the item is already in use? shouldn't be to hard to integrate..

edit: just updated the file with 0..1 values for the presets module after this was in discussion too, and added a properties panel

[Nubeat7]

reuploaded the last version, just did a few improvements and optimizations in the code.. so the item name output comes also from the ruby module now..