That is what I figured. I was thinking if you wanted to perhaps be a bit reckless, you could try to figure out the flashlight without an SDK hook. But any such code should probably be updated once SDK hook is available. So yeah, it seems prudent to wait for the SDK. But a man can dream right 
Looking forward to your new module. I think it will be popular.
It’s worth noting that a certain “Ben” is famous for making impossible modules. I assume he is doing things not in the sdk?
I’ve never used the sdk, so I don’t know what’s in there. But it’s always been pretty easy to reach inside rack and do magic. Don’t know if this is in that category.
Hmmm, just had a thought, the module changes the Rack values directly based on the params.
Not entirely sure what would happen if you added more than one instance of the module… there would be no reason to do this, but I’m not sure there is anyway to prevent multiple copies of a module.
I guess whichever module gets processed last would take precedence.
Any devs know how I can detect existing copies of the module?
I love you.
Talk to @k-chaffin his module is a Singleton. Don’t know if that’s the recommended way to do it though.
Glad to help.
As pgatt mentioned, my PurrSoftware Meander module is implemented as a singleton due to its use of global variables since it was once a Windows app. Andrew guided me a couple of years ago on how to make a singleton and the technique works very well but it is not trivial even though it is fairly straight forward. One complication is that you have to handle the situation of the user actually trying to add a 2nd instance. You either have to do nothing and confuse the user, or display some type of disabled module that tells the user what the deal is. This last is what Meander does.
Ah, glad you found the thread. I had forgotten that was around.
I would think an easier and less confusing option would be to just make multiple instances work. If your knobs follow the actual setting in rack, and only change it when a knob moves, then multiple instances would always have the same value.
This doesn’t work with how I have coded the module, I am directly setting the Rack value from the parameter + CV value, multiple instances overwrite the value on each process step.
The master instance is easy enough to implement, so I’ve done that, currently only the master instance gets ports & knobs. Once I’ve done the full panel design, I will add a label that indicates why the non-master instances do not do anything.
I’ve got a quick Windows build here for anyone that wants to give it a bug bash. (I may have a Mac build later if I find the time…) Release bright-idea-v1.0 · Miff-Real/DanTModules-Manual · GitHub
I think I need to add a feature to deactivate the module when the module browser is open, because its quite annoying not being able to see when adding modules to a patch. Is there any knowledge on detecting the module browser?
There should be more than enough room to add a parameter for the flashlight, should that be added to the API.
You might look in my Meander.cpp file on my GitHub repository as I handle this. Look in the MeanderWidget constructor where I mention what I did to get the panel to display in the browser when there is no module instance due to being a singleton.
Actually, I misinterpreted what you were asking, I think. My comment had nothing to do with Room Brightness, etc.
I added the GitHub workflow from Automated building and releasing Plugins on Github with Github Actions to my repo and it seems to work, so I have made a new test build for Windows, Linux & MacOS (although the Linux build was made with ubuntu-latest which I’ve read can cause issues)
After a little digging in the API and Stoermelder PackOne, I think this may work: APP->scene->browser->isVisible()
Hi,
thanks for the newly added Bright Idea module.
When loading an instance into the patch, the module takes over the current settings of the parameters.
But when clicking the ‘active’ button from the default ‘on’ state to ‘off’, and then back to ‘on’, all parameters are set to a max setting.
Is this intended? I would prefer if maximising the value’s didn’t happen.
It was intended, but I am working on a new version that will have some additional context menu options to let you configure how the module works. (The new version will probably not be available until some time Saturday because it’s nearly beer o’clock where I am).
Override Rack off by default - Controls the values when the module is added to the patch, activated, or when the module is un-bypassed. When this is off, the module will set it’s parameter values to match the current Rack settings, ignoring any changes to the parameters that may have been made while the module was not active. When this is on the current module parameter values will be used, ignoring any changes to the Rack settings that may have been made while the module was not active or bypassed.
Deactivation Defaults on by default - Controls the values when the module is deactivated or bypassed. When this is on the Rack default settings will be restored when the module becomes inactive. When off the values of the parameters will not change. Rack default settings are: float cableOpacity = 0.5; float cableTension = 1.0; float rackBrightness = 1.0; float haloBrightness = 0.25; as seen here Rack/src/settings.cpp at b3b7b652c1e4832e169afc8578747a33929c0caf · VCVRack/Rack · GitHub
Module Browser Deactivation on by default - This option will temporarily deactivate the module while the module browser is open. Note, this is independent of the Active Toggle button & CV.
And you can see that the module has my traditional CV Param Mode & CV Input Slew options as well.
Obviously these new menu options add a lot of extra use cases for saving & loading patches, both in VCV and the VST, especially where you may change the Rack settings between save and load. So far I have really only tested using the module directly in a patch, so any additional testing reports would be gratefully received.
Excellent!
Enjoy your beertime 
VCV Youtube videos are about to get more fun. Very cool ideas. I love the recent mods too. Cheers!
Well it took me awhile to figure out the dynamic text for the module state, but I finally just finished the update.
Here are the new builds (note: the Linux build is still done on ubuntu-latest so might not work, I haven’t tested it) Release bright-idea-v1.1 · Miff-Real/DanTModules-Manual · GitHub
edit: I just noticed in that screenshot that the slider lights are funky on both WAVULIKE and VCV RANDOM, I guess that’s a bug?
Hi Dan,
i just had a quick look at the module.
Thanks for adding “deactivation defaults”.
Still the button “bypass on/off” doesn’t work as one would expect,
for example:
If i have my custom value’s set for the screen in Rack itself, and i adjust the settings in your module (while deactivation defaults in enabled).
And then click the bypass button to OFF, i would expect the settings of the module to take over (this happens and is ok).
And when clicking the bypass button to ON i would expect the settings which were default in Rack itself to take over (this does not happen).
That would be a bypass,
but right now the bypass button works as a reset.
Maybe i missed something? Or what i describe is technically not possible?
Eitherway thanks for the module
