From the original SynthMaker forum (2004–2014), with its members’ names and dates.
Tom7777 ·
I have a few schematics like a game i was making and some other things that use the Mouse Click modules and Redraw Area, it would seem as if certain schematics will now not work correctly unless you add a new Redraw module if using module layers and the redraw data will not pass through correctly. Im ok now with this since adding a new redraw is quite simple but it would seem as this is a bug maybe. Basically if you have a module with a To Parent connected to the MGUI module it won't send the view data through unless new modules are added. I noticed that you said something like this for New Release 0.9.3o and it is probably to do with this but i report all bugs i find just in case. Thanks 🙂
malc ·
I'm not sure what you mean Tom. Do you have an example?
It's certainly true that older schematics may need redraws to be inserted.
Tom7777 ·
Well it fixes when i change to the regular redraw and not redraw area and as always i have found a work around and spent about 2 hours thinking about different solutions so everythings cool now. A lot of the bugs i have found i think are due to when modules change so i have had to update various things quite a lot. I also think some things i find may be becuase i could possibly be taking SM to it's limits in terms of what is possible. Basically this bugs fixed for me but i can send a more simple version of this if you want it as the version i get the error with is about 6 times bigger than the example project and i don't really want to send that. Thanks 🙂
malc ·
That's good Tom, although if it's a bug and you fixed it then I assume you mean that it's a bug in your schematic and not in the software? If it's a bug in the software then I'll need to look at it.
The regular redraw isn't currently doing what it's supposed to. Currently this redraws everything all the way up the hierarchy when it should only redraw the area of the module that it's attached to. As it stands the Redraw component is unusable in general because it causes too many redraws and really slows things down in all but the most simple of schematics.
I've fixed the Redraw for the next release so you may find that whatever problem you're seeing will return unless I have a look at what the issue is.
Tom7777 ·
Arrgg i just loaded and a schematic edited it to send with comments i was writing and saved over the project by mistake 🙁 it took about 2 days.... im not in such a happy mood at the moment but i will send some schematics today probably.
bones ·
Its also a bug in FM3x - you can select a new waveform but the GUI doesn't update so it always looks like its the default selection.
malc ·
Yeah, we forgot to update the example for the last release, sorry about that.
jorge ·
bones wrote: Its also a bug in FM3x - you can select a new waveform but the GUI doesn't update so it always looks like its the default selection.
The redrawing is fixed on the Moog Ladder filter version of the example file:
[old link]
bones ·
The FM3x is still not updating the GUI when you select different oscillator waveforms.
Shifrin ·
I don't have a lot of free time today, but I get an update bug with my own bitmap-strip knob, which triggers a redraw-area every time it is updated. This has only happened since the 'force' redraw stuff was implemented. But as far as I can tell I *am* forcing a redraw!
If I get the time I'll post it later, or tomorrow 🙂
Shif.
malc ·
Thanks Shif. I loaded up the knobstrip.osm example you did a while ago and that seemed to be working fine in the latest r release. So if you have another example that exhibits problems it would be really handy to see it.
Shifrin ·
Afaik the one on-line uses a Redraw and you or jorge suggested using a RedrawArea, which is what I am now using in it, and having problems with. I'll send you the .osm tomorrow it's not on the machine I'm using for the .net right now 🙂
Cheers!
Shif.
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker