Page 2 of 4

Re: Exclusive Selector- Halp?

Posted: Thu Sep 11, 2014 9:54 pm
by Nubeat7
Perfect Human Interface wrote:Here's the current (hopefully fully fixed & working) version if anyone wants it.

seems to work well as long as you don't put a presetmanager inside, all presetmodules reporting an error then!?

Re: Exclusive Selector- Halp?

Posted: Thu Sep 11, 2014 9:58 pm
by Perfect Human Interface
Nubeat7 wrote:all presetmodules reporting an error then!?


Could you explain? Is this related to those blinking drop-shadows?

Re: Exclusive Selector- Halp?

Posted: Thu Sep 11, 2014 10:01 pm
by Nubeat7
i got this red white frame around every selector when putting a presetmanager inside, the errors are happening in the preset module of the selectors, don't you have the same problem? (i'm using fs 3.05)

Re: Exclusive Selector- Halp?

Posted: Thu Sep 11, 2014 10:09 pm
by Perfect Human Interface
Nubeat7 wrote:i got this red white frame around every selector when putting a presetmanager inside, the errors are happening in the preset module of the selectors, don't you have the same problem? (i'm using fs 3.05)


No, but I get blinking drop-shadows (version 3.0.4). Maybe that really does mean an error.

Try this version. I had deleted the "MIDI CC" bits in the preset module earlier while trying to figure out what was going on. Don't see how it could have made a difference but I reverted to the original preset modules and they don't blink.

Re: Exclusive Selector- Halp?

Posted: Thu Sep 11, 2014 10:16 pm
by Nubeat7
ok, there is no errormessage now, but the presets are not recognised correctly when recalling presets...

the ruby version i did seems to work well also with the presets, here it is with a presetmanager included

Re: Exclusive Selector- Halp?

Posted: Thu Sep 11, 2014 10:40 pm
by Perfect Human Interface
You're right of course, and in my haste I neglected to test for that. I did forget to rename the preset params for each selector after reverting the preset modules, but that didn't make a difference.

One thing I noticed with your ruby drop-down, though it's hard to recreate consistently, is that the text displayed flickers between new and previous sometimes after changing values.

Re: Exclusive Selector- Halp?

Posted: Thu Sep 11, 2014 10:41 pm
by Nubeat7
btw wouldn't it be preferable that if you cannot select another item on a selector because it is in use, that it stays at the old item instead of changing to 'none'? like there will happen nothing if the choosen item is in use already.

this is also no problem to realize in the ruby version, you only need to choose @check when item is used:

just change this

Code: Select all

outIdx = check_if_used(index) ? 0 : index

to this

Code: Select all

outIdx = check_if_used(index) ? @check : index


like this:

Re: Exclusive Selector- Halp?

Posted: Thu Sep 11, 2014 10:47 pm
by Nubeat7
Perfect Human Interface wrote: though it's hard to recreate consistently,

what do you mean with that?
Perfect Human Interface wrote: the text displayed flickers between new and previous sometimes after changing values.

don't get this issue here..

Re: Exclusive Selector- Halp?

Posted: Thu Sep 11, 2014 10:49 pm
by Perfect Human Interface
I mean that issue is hard to recreate consistently. When I play with it for a while, eventually I'll see it happen, where it just flickers for a moment. I don't know what causes it.

Re: Exclusive Selector- Halp?

Posted: Fri Sep 12, 2014 12:09 am
by 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.
Tried to recreate it in all green but my computers come down with a serious case of lag making testing trigger orders impossible, will try again after I've wiped the drive.