Thanks for the feedback. I guess this was an issue of using a different PyQt library version. Could you please try the new file I have uploaded?
Dominic
Ok now
couple suggestions:
start button, after it starts could it change to pause, then when paused to restart?
when paused the time changes to show thousands of seconds but only whole seconds when running,
thanks,
Thanks for you suggestions:
"start button, after it starts could it change to pause, then when paused to restart?"
As I am not sure whether this is another version problem: The program does more or less what you describe, except that the button gets the labels "Start" and "Stop".
"when paused the time changes to show thousands of seconds but only whole seconds when running,"
That happens on purpose: First, updating the milliseconds frequently (lets say as fast as possible) would consume CPU power and would result in flickering. And second, one cannot read the milliseconds while they change permanently, anyway. I think this looks nicer and provides the same degree of functionality. After all, I just wanted to have a simple stop watch. ;-)
Ratings & Comments
4 Comments
python qstopwatch.py Traceback (most recent call last): File "qstopwatch.py", line 93, in slotBnStartClicked print "start "+self.startTime.toString() TypeError: cannot concatenate 'str' and 'QString' objects
Thanks for the feedback. I guess this was an issue of using a different PyQt library version. Could you please try the new file I have uploaded? Dominic
Ok now couple suggestions: start button, after it starts could it change to pause, then when paused to restart? when paused the time changes to show thousands of seconds but only whole seconds when running, thanks,
Thanks for you suggestions: "start button, after it starts could it change to pause, then when paused to restart?" As I am not sure whether this is another version problem: The program does more or less what you describe, except that the button gets the labels "Start" and "Stop". "when paused the time changes to show thousands of seconds but only whole seconds when running," That happens on purpose: First, updating the milliseconds frequently (lets say as fast as possible) would consume CPU power and would result in flickering. And second, one cannot read the milliseconds while they change permanently, anyway. I think this looks nicer and provides the same degree of functionality. After all, I just wanted to have a simple stop watch. ;-)