From the original SynthMaker forum (2004–2014), with its members’ names and dates.
Tom7777 ·
Does the mouse moves input effect the schematic if its not had any inputs? so will it effect older projects that use mouse event or will it only be activated if a bool/int input is made? i really hope it won't do as i will have to update loads of projects if this is the case, Will i need to update older projects which use mouse move by setting it to 1 so the mouse events function correctly or can i leave it as it is and they will still work the same way, i noticed that with a new project if you use a module like Mouse Over you will have to set it to 1 for the events to work, i know that it was added to save cpu in synths but to be honest i find it quite annoying having to set it each time now as i will sometimes forget and then think i have found a bug or made a error somewhere in my project untill i remember that the new inputs there 😕
oddson ·
According to the release notes for 0.9.5h it will cause problems for old schematics that don't use the wireless front panel.
I guess that explains why some of my old sh*t isn't working...
I think all you have to do is attach a TRUE boolean to the MGUIs of the front panels or switch them to the wireless method.
Tom7777 ·
I think all you have to do is attach a TRUE boolean to the MGUIs of the front panels or switch them to the wireless method.
If theres more than one layer im guessing that you would need to do it for each one. Its definately one of the annoying things about the program when you find out your going to have to edit about 30-40 schematics just so they work ok again 🙁
oddson ·
Actually, it may not be as bad as that... I've just opened one of my older projects and it's working even though it seems to fit the bill for one that shouldn't. So there's something about this that I'm not getting.
EDIT - old schematics that I'm pretty sure weren't working under 'i' and 'j' are working under 'k'. Could it be Malc has left that feature disabled on this version ('k')?
Tom7777 ·
Hopefully it works like the features disabled unless there is a bool or int on or off status connected, im guessing it might be this way but i would like confirmation, if it doesn't work this way please make it do so. As its a feature for saving cpu it should function this way as its really only needed when you optimize a schematic so rather than having to input a value of 1 for mouse events to work it should start with the mouse functions working and then if you don't want them to work to save cpu you set the option rather than it being there from the start which im guessing is the way it works as i recently made a mouse over event which required me to set it to 1 for it to run. I don't like it that way, please change it if possible, thanks
malc ·
The switch is just for Mouse Move messages on their own. You only need to enable it if you want to use the Mouse Move or Mouse Over components. All other mouse messages are unaffected by this switch.
When doing this we had to decided whether it was more likely that someone would be using the Mouse Move/Over components than not. Since none of the supplied controls (knobs, sliders etc.) use Mouse Move or Mouse Over and these are widely used, it seemed obvious that the default should be to turn mouse move messages off.
I hope that you'll understand Dan that we had to go for the option that would cause the least amount of disruption to the fewest number of people. Sorry if this causes you more work, we really do try to keep these kind of changes to the bare minimum.
Tom7777 ·
The switch is just for Mouse Move messages on their own. You only need to enable it if you want to use the Mouse Move or Mouse Over components. All other mouse messages are unaffected by this switch.
Ok at first i thought that it must be all mouse data/modules so now the problem doesn't seem so bad now but i will still have to sort through and fix various things but it's ok, thanks for the information Malc 🙂
oddson ·
Tom7777 wrote: ...at first i thought that it must be all mouse data...
Me too, and that preception was strengthened by the fact that I could not get any of the controls for the 'classic' synth to work one day... I assumed it was some upgrade that left it incompatible but since I was only in it to see a signal module I didn't give it much thought.
Did anyone else notice any old synths (that don't use the mouse-move/hover) that weren't working for a while?
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker