From the original SynthMaker forum (2004–2014), with its members’ names and dates.
NothanUmber ·
The "Int Equals" component returns an unexpected result.
How to reproduce it:
* create two int data components, enter a "0" into the first one and a "1" into the second one.
* create a string data component
* create a int equals component
* connect the two int data components as inputs and the string data component as output to the int equals component
The result will always be "True" no matter which values you choose for the two int data components.
Greetings,
NothanUmber
jorge ·
Thanks for the bug report NothanUmber
I think that bug has been fixed in our latest internal version of SM which you can download from:
[old link]
or if you prefer rar compression:
[old link]
Please note that the DirectSound works different know as I explained in the following thread:
CSMMidiReciever::OnError > short
NothanUmber ·
jorge wrote: I think that bug has been fixed in our latest internal version
Yes, now everything works as expected (Though if one loads an oxm-File that was created with SM 0.9.1a with unequal input values for the "int equals" component it continues to show "True" even if one enters other pairs of unequal values. But if one provides a true equal pair once the component works correctly from now on.)
malc ·
NothanUmber wrote: Though if one loads an oxm-File that was created with SM 0.9.1a with unequal input values for the "int equals" component it continues to show "True" even if one enters other pairs of unequal values
That's a good point and it's something everyone should be aware of. If we fix a bug and release a new version then schematics produced prior to the fix may sometimes need tweaking to get them to work properly. I think this is more the exception than the rule but it's certainly worth knowing.
It's an unfortunate but unavoidable problem I'm afraid. Better to get the problem fixed though. Also more basic problems like the one yo've highlighted will get ironed out as we progress through the beta testing.
On a similar note, we've made some big improvements to the graphics performance for the next release (I think these are in the internal version Jorge posted above). These changes required the example to be modified to take account of the fact that module GUIs are now clipped to the module's client area. So you may have to make some small changes to any GUI stuff you've been doing.
Wrote something here? To have a post removed or your name hidden, write to [email protected].