In Netlinx I am doing 24 hours, that's 864'000 1/10 of seconds... I'd say the wait time is a LONG, the same data type returned bu GET_TIMER.
The max value of a long is 4,294,967,295 or about 13 years...
If you are on NetLinx Systems, you should definitively use Timeline It's a lot more efficient and accurate than Wait, and it's really not difficult to use.
Originally posted by frthomas In Netlinx I am doing 24 hours, that's 864'000 1/10 of seconds... I'd say the wait time is a LONG, the same data type returned bu GET_TIMER.
The max value of a long is 4,294,967,295 or about 13 years...
Fred
Would be a shame to CANCEL_WAIT after 12 years, 11 months...
Originally posted by vincen If you are on NetLinx Systems, you should definitively use Timeline It's a lot more efficient and accurate than Wait, and it's really not difficult to use.
Vinc?n, do you get a dollar from AMX everytime you advocate TIMELINEs on the forum :-)
TIMELINES for sure use LONGs and are in millisecond, so the max wait time there is shorter: only 49 days...
Really guys these are just random thoughts and fun calculations, do not plan your next project on my values unless some AMX guy chimes in with the correct model...
Charles Law
Posts: 72
Comments
The max value of a long is 4,294,967,295 or about 13 years...
Fred
That's one heck of a WAIT
-- John
Vinc
Would be a shame to CANCEL_WAIT after 12 years, 11 months...
Vinc?n, do you get a dollar from AMX everytime you advocate TIMELINEs on the forum :-)
TIMELINES for sure use LONGs and are in millisecond, so the max wait time there is shorter: only 49 days...
Really guys these are just random thoughts and fun calculations, do not plan your next project on my values unless some AMX guy chimes in with the correct model...
Fred