Page 2 of 2

Re: presetmanager bug or normal behaviour?

Posted: Sun May 11, 2014 7:10 pm
by RJHollins
just getting to look inside ...

Code: Select all

don`t forget to trigger also at the output to update the slider or knob 

hmmm ... something I did forget during my attempts :|

The one I need to really look at is your multi-function slider, and now seeing how you've implemented the reset to a defined 'Default' position.

This is a very nice feature to have available for sure.

Last nite I work on an idea to include a 'Message/Alert Box' added to the INIT/Reset button. The idea was to have confirmation that a reset was indeed wanted.

I have posted that addition into the example. I found that this was not as straightforward as I had thought it would be. The MsgBox doesn't have an 'internal' reset of its state, so I had to attach a 'switching' logic to monitor the user choice and only send the 'Reset trigger' on 'YES'. [maybe I made this more complicated than needed, but seems to be working].

Thanks once again NuBeat ! :D

Here's the schematic:
init program+array [with MsgBox - RJH]-1.fsm
(156.04 KiB) Downloaded 813 times

Re: presetmanager bug or normal behaviour?

Posted: Sun May 11, 2014 9:30 pm
by Nubeat7
cool, thats a good idea,
you also can modify the ruby trigger button and open the message box directly there..
with the ruby version you can also send just a trigger to the output no need to workaround some states

Re: presetmanager bug or normal behaviour?

Posted: Sun May 11, 2014 11:46 pm
by RJHollins
:o That's all that needed to do this with RUBY !??! :shock:

:lol:

I'm laughing cause of the amount of time it took me to get the PRIM idea working :roll: I'm certain that my prim use was a crude solution, and could be done much simpler ... but this RUBY solution is a far cleaner code. :mrgreen:

Thanks for doing that !

Now to study the multi-preset mod you provided.... that ... and I must keep working RUBY stuff more !
8-)

Re: presetmanager bug or normal behaviour?

Posted: Mon May 12, 2014 5:09 am
by RJHollins
This is working nice NuBeat ! :D

Even simpler ... having a 'Reset INIT' within a module allows for just that module to be affected. Now, placing another Reset button above all the separate modules, adding a wireless 'masterinit' out, while tagging a wireless 'masterinit' to the trigger of the inside modules now provides for both separate, AND a Master INIT reset. :o We can reset one ... or all.

beautiful :mrgreen: