pall ·
Hi! I present two vector sliders realized recently. They differ somewhat of the known, both in appearance and functional. But hope you will like. 😉
From the original SynthMaker forum (2004–2014), with its members’ names and dates.
pall ·
Hi! I present two vector sliders realized recently. They differ somewhat of the known, both in appearance and functional. But hope you will like. 😉
oddson ·
Sweet! 😍
I've made similar-looking sliders myself but yours looks like you've done a much more thorough job than I ever did.
trogluddite ·
Nice 🙂 Better than the stock ones IMHO. I always liked the "bar graph" type better than ones with a handle - much easier on the eye, especially when there are lots of them, and I find them quicker to "read" when scanning a panel. Good that you can just click for a quick setting too - I know that isn't everyone's cup of tea, but I hate when I need to quickly 'kill' a parameter, and my mouse just can't seem to find some stupid fiddly little grabby thing.
ChrisHooker ·
On my system the vertical one seems to have the mouse's Y values reversed on click. (Dragging works fine.)
ChrisHooker ·
Needed to subtract the LDown value from the height of the module. Updated version attached.
trogluddite ·
Seemed right in the original one to me - but I think maybe the number readout should be at the bottom (on the darker part), to make it more obvious that it is like the horizontal one (dark bar = value, light bar = background). Having the number on the light part, does kind of give the impression that it might be reversed.
ChrisHooker ·
Hmm.. maybe a difference between SM versions? Does my alteration not work correctly for you, trog?
P.S.: I never said "Nice work, Pall!" ... so - Nice work, Pall! 🙂
oddson ·
The numeric display seems to disappear on me sometimes when I zoom around with the mouse.
This is nice work... definately worth working out any little bugs.
trogluddite ·
ChrisHooker wrote: Hmm.. maybe a difference between SM versions? Does my alteration not work correctly for you, trog?
Weird - I have precisely the problem with yours that you had with the original - dragging fine, but upside down click-to-set. Your "height minus click" method is what I usually use, but in conjunction with a negative sensitivity for the Y-drag - converting from up to down prior to the DragY rather than after it, so to speak - but I can't see any reason that pall's method should not work. What SM version are you on? - I have 2.0.5 Professional here. I tried disabling the "new trigger system" (Ctrl-Shift-Alt-T), and a few other things, but nothing so far that makes either schematic behave any differently.
trogluddite ·
Here's a quick test schematic - just a draggy box. On my system dragging up makes the number go down and vice versa.
@Chris - you aren't by any chance using a 'mousing device' that uses custom drivers? I just ask because I had similar problems with an old Logitech trackball a while back (not in SM though) - really unpredictable which app's would play nicely with the custom settings.
ChrisHooker ·
LOL - I'm on 2.0.0 Pro. Haven't updated for precisely this reason - unpredicability with existing schematics, and I haven't seemed to need any features in the updates.
On the other bug you found - it seems the numeric display turns off if you drag the slider outside its window. Happens in both horiz and vert. I'm not sure how to fix that either.
ChrisHooker ·
Trog, your drag test works the same here - drag down, the number goes up.
Try this: I just added a Mouse LDown prim to it. When you click visually lower, does it give a higher # than if you click high? (That's how it works here.)
ChrisHooker ·
trogluddite wrote: @Chris - you aren't by any chance using a 'mousing device' that uses custom drivers? I just ask because I had similar problems with an old Logitech trackball a while back (not in SM though) - really unpredictable which app's would play nicely with the custom settings.
Good thought, but no, I'm just using the tracking pad on the laptop, nothing customized, no added drivers.
oddson ·
ChrisHooker wrote: Try this: I just added a Mouse LDown prim to it. When you click visually lower, does it give a higher # than if you click high? (That's how it works here.)
That's how it works everywhere... Origin is upper-left corner.
ChrisHooker wrote: On the other bug you found - it seems the numeric display turns off if you drag the slider outside its window. Happens in both horiz and vert. I'm not sure how to fix that either.
The problem is there is a boolean switch on a MouseOver for the display but when you drag outside it stays TRUE until you return and then it goes FALSE (somewhat counterintuitive!). Can be fixed by adding an OR with the Dragging output from the Accumulator.
pall ·
Thank you guys! 🙂 I think we can make improvements in these sliders, such as the sensitivity, snap, steps and other things. If it can and if necessary.
ChrisHooker ·
oddson wrote: That's how it works everywhere... Origin is upper-left corner.
Yeah, that's how it SHOULD work everywhere, but as we're having opposite results in the full schematic, we're just trying to troubleshoot where the difference between our two systems is - starting with bare-bones and adding the complications one by one.
ChrisHooker wrote: On the other bug you found - it seems the numeric display turns off if you drag the slider outside its window. Happens in both horiz and vert. I'm not sure how to fix that either.
oddson wrote: The problem is there is a boolean switch on a MouseOver for the display but when you drag outside it stays TRUE until you return and then it goes FALSE (somewhat counterintuitive!). Can be fixed by adding an OR with the Dragging output from the Accumulator.
Niiice. Thanks for that. Here's an update with that, the readout positioned at the bottom, and for the time being, the change I made to get the 'on-click' value correct.
trogluddite ·
@Chris - yes your test works fine here on 2.0.5. Been using SM since before v2.0, so I tried a few of my very old schematics - but yet to find anything mouse related that seems to have changed.
trogluddite ·
Maybe onto something here... During re-sizing of the module (pall's original), the slider bar inverts, when I release the handle to finish re-sizing, the graphic goes back to normal - and there's also a quick toggle of the slider's output value. Within the little wireless "Size" module, i added a Sample and Hold, followed by a trigger blocker to the width and height values - to block triggers in both directions - and the re-sizing weirdness goes away. (just a lucky bodge, too long a day at work today to begin to understand why this is happening!)
I have a hunch that something similar is happening in the older SM, but during the click as well - some sort of spurious triggering from the view area that is messing with the DragY. Here's pall's original schematic with the bodge (to be treated as an experiment, not a robust fix!!)...
ChrisHooker ·
Didn't seem to solve the LDown directionality problem on my end. It DID cause some redraw errors, though! 😉
DigitalWhiteByte ·
some improvements: stop line, up-down Mouse over for value, now work other ....
ChrisHooker ·
That one exhibits the same reversed position LDown on my system, so there must be something screwy on my end. I'm just not bright enough to figure it out. The math seems correct to me with my Height-LDownValue mod, so I have no clue. Oh well, it's not like I'm selling my creations.
ChrisHooker ·
Actually, I will add this: When using my own mod, when I left-click and hold down (but don't drag yet), the output value is momentarily reversed from what it should be (assumingly, how you guys see my mod as acting), however the MOver readout shows the correct value and the bar also displays in the right place. As soon as I release the L mouse button, or if I start dragging, the output value updates correctly.
pall ·
I'm sorry boys, that the sliders does not work properly, especially with preset manager. On the horizontal I made some changes and it seems works correctly. I hope. 😉 But in the vertical happen strange things. 😈 Yet I believe we will solve these.
ChrisHooker ·
I can't even open that one. Must have a new module or som'n. Can you describe what you changed to the horiz?
pall ·
As shown in capture. Using preset manager display values was not correct...
ChrisHooker ·
Thanks, pall. What's the new output in the "Set" module? The Set value, direct from the wireless?
pall ·
In the previous schematic the value from preset manager not appear in output, implicitly in green value display (mouseover). So I put to output a float switch to which I drew a link from the wireless (Set) connector. I would be glad if you would confirm that it works well.
ChrisHooker ·
For the horizontal, that fix seems to work well with loading presets. Doing the same for the vertical, I get the bar flipped (1-value) (but only when loading from preset, not when clicking/dragging), but the readout and output are correct when a preset is loaded.
(My [height-LDown] mod is active in this, but disabling it doesn't change how preset handling/results work.)
ChrisHooker ·
Ok, here's another version that on my machine fixes the vert slider's preset handling, AND it removes the [height-value] flip that I needed before to get the mouse click to work right. ...So hopefully everything should be compatible now with everyone's setup? Let me know.
pall ·
This is great Chris! 😍 And you perseverant. It seems the thing is almost solved. I moved you'r Float Subtract from the Preset mudule output, to the Set module, with the intention, that the Preset module to remain original. I solved the values display to occupy the bottom of the window whatever its size. And in the end I did a check with the Preset Manager with six presets. It seems to work well.
ChrisHooker ·
Good news - I can open that one! lol
Nice catches. I found another one - the way I had it set up flipped the "Set" value twice, and that's just extra math. So, instead of routing the 1st flipped Set to the rest of the main operations (where it needed to be flipped again to work), I just routed the original (unflipped) Set value, and got rid of the 2nd flip.
I also realigned the vertical readout position so it sits just inside the bar.
Now here's a question for ya - and maybe it deserves its own thread, but - I've never been in full understanding of the way the preset manager works - how do you add presets to the list, so that you can see more than one on the dropdown?
pall ·
To have more presets, open Properties panel, and for Total, choose number of presets that you need. To have ready-made presets proceed in the following steps; -choose from list a some line (click). If still no presets it is understood that the first line is chosen. -be made settings desired. -and choose a name for this preset (click on Name button, and type) If you managed to make a SUPER preset 😍 it's good to be saved on disk. In the Properties panel you may choose the lock option when you do not want to screw the SUPER preset. Cheers!
ChrisHooker ·
Very cool. Thanks so much!
ChrisHooker ·
Ok, a little more work done...
- Added [CTRL + L-click] functionality for setting to default value.
- Added [SHIFT + drag] functionality for fine adjustments.
- Preview (shown on properties page) was truncated to the preview module size (MGUI), so resizing the properties panel didn't reveal all of the slider preview if it was set large. As a result, values changed to what looked appropriate in the preview could be different than the actual value, as shown when exiting preview. I changed the preview size to match the size of the main GUI, to avoid visual confusion and allow visability of any truncated parts by simply resizing the property panel.
Steps, Snap not done yet... I'm sleepy and going to bed, and honestly, those confuse me a bit... at least right now. Once those are done, though, I think this project will be complete!
...Until someone wants a DIAGONAL vector slider!!!! 😮
P.S.: In this osm is also a modified version of the preset manager. Feel free to use.
Wrote something here? To have a post removed or your name hidden, write to [email protected].