JeremyK, for me this is some nonsense what You are doing - when new value of slider is 0 You are once more set it to 0. I suspect that the other methods are identical. What you really want to do?
JeremyK, for me this is some nonsense what You are doing - when new value of slider is 0 You are once more set it to 0. I suspect that the other methods are identical. What you really want to do?
You have a slider with a range of zero to four, but are complaining about something with a value of 10, 30 or 40?For instance, if I move it to say 10, it works but then stays there regardless of moving the sllider. All of a sudden, it then jumps to 30 or 40. Any idea why?
The jerky behaviour is probably because whatever is executing in the slots associated with 1, 2, 3 etc. is taking some time to execute and blocking the UI while it does so. The slider emits a valueChanged() for every value you pass through, not just the value where you release the slider button.
Ultimately though I have no idea what you are trying to achieve. The whole idea of using the position of a slider to execute discrete functions more logically assigned to buttons is truly odd. If you want all five actions to occur in sequence then just call the slot for each button in turn in response to pushing a "Do the lot" button.
JeremyK (19th May 2013)
Bookmarks