From the original SynthMaker forum (2004–2014), with its members’ names and dates.
rl ·
Test 1: use the example synth. Add more "stripes" (e.g. 32) to the LFO. Change values by quickly moving the mouse. Not all stripes are updated.
Test 2: use Toms Web Button ([old link])
Mouse over the button and quickly move the mouse away from the button. The Button remains in "Mouse over" state.
In both tests it seams that "Mouse Event" components (Drag, MOver) cannot follow fast mouse movements.
pls. fix, or is there a workaround?
jorge ·
rl wrote: Test 1: use the example synth. Add more "stripes" (e.g. 32) to the LFO. Change values by quickly moving the mouse. Not all stripes are updated.
pls. fix, or is there a workaround?
Yeah, there is a workaround. The inefficiency is not related to SM itself but to the schematic. Each time you drag the mouse on top of the bars, it generates a redraw for the full area:
Redrawing the full area seems to be enough for a small number of bars as in the example synth.
Some time ago I did a more efficient version where the redraw area was a much smaller area of just the current bar changing, it was a lot faster.
We decided to give low-level control over the redrawing because it makes a big difference to GUI responsiveness but it means users have to use it in an efficient way.
malc ·
Hi rl,
rl wrote: Test 2: use Toms Web Button ([old link])
Mouse over the button and quickly move the mouse away from the button. The Button remains in "Mouse over" state
Are you using the very latest version (0.9.3f?). The reason I ask is that I fixed a bug which was causing exactly the behaviour that you're describing. Of course I may have made a mistake, but try as I might, I just can't repeat the problem here.
Thanks.
Tom7777 ·
Update to the latest version if you still get the error you can kind of fix the error by making the transparent area much bigger that way it won't skip it as easy. I did say to Malc about this before the example went online about if you move the mouse fast, and there was also another error with the Mouse Over module which has now been fixed in the latest SM 🙂 Hope this helps
rl ·
Are you using the very latest version (0.9.3f?)
Sorry, forgot my daily update. Web Button Works now.
The inefficiency is not related to SM itself but to the schematic
I see
Thanks for the answers, will have to change my schematic.
rl ·
Update:
I tried to improve the schematic as suggested. I experimented with different RedrawArea's but with no success.
Get the schematic here
It's an attempt to create a wavetable oscillator with user drawable waveforms.
In the window a sinewave form was drawn. Moving the mouse slowly (left side) everything is ok. On faster mouse moves (right side) not every stripe is redrawn at the new position:
There is another problem:
When clicking on some place (marked as "clicked here" the stripe is redrawn with a wrong value (marked as "redraw here" ). The funny thing is, that the y-position (botton value) display is right. On a second click (same position) the strip is displayed correctly
Again, I don't know whether it's a bug or a feature.....
Any help would be appreciated
skOre ·
First guess would be that it has got something to do with the mouse tracking component within the module... I think the drag would work with what you proposed, but maybe the click is still specialized on the half height...
Wrote something here? To have a post removed or your name hidden, write to [email protected].