Mostly, these 3 report the time, and this would be great for a project I am working on; if someone tells me how to make the blocks it would be helpful.
I need it in version 1.4, hope it comes out in 2.0!
Last edited by rdococ (2010-08-11 05:57:21)
Offline
well you con do this by: wait one seconds change [seconds] by one. wait sixty seconds change [minuetes) by one. wait (however many seconds are in an hour) change hours by one. and put it in a forever loop.
Offline
That's a wonderful idea! I definitely support this Think of the possibilities - projects that adjust how they look depending on the time of day! Ah, wonderful!
My only suggestion would be to have it as a drop-down block, so as to not waste valuable space What category do you think this would go into?
@FlameInc - I think what rdcoc was suggesting was that it would report the system time, not something along the lines of "timer."
Offline
FlameInc wrote:
well you con do this by: wait one seconds change [seconds] by one. wait sixty seconds change [minuetes) by one. wait (however many seconds are in an hour) change hours by one. and put it in a forever loop.
Like coolstuff said, he's looking for a system clock-type block, not a timer. And I wouldn't recommend using the "Wait _ seconds" block for any sort of timekeeping, as it is extremely inaccurate.
Offline
Useful for the timer related stuff I've been trying, I say yes.
Offline
lasc12 wrote:
Good idea! I support. Would this be on system time or PST or what? And how many blocks would be needed? And what section? Probably Sensing.
The timer works by counting from the last reset (or when you opened the program if there's no reset, I think. Not sure if it's saved), so this would be no different apart from also having minutes and hours.
Just one question: let's say 120 seconds have gone by since you reset the timer. The minutes count would be 2, would seconds be 120 or 0? Or 30 seconds. Minutes count is 0.5 or 0?
Offline