Currently, if you enter a value greater than 65535 as a "dragSpeed", execution fails and an error is thrown. I see that it indicates that 65535 is the maximum value in the documentation, but should it throw an error? The documentation does not say it will.
I vote that it is an unhandled exception to be corrected, and instead should fail gracefully and report into "the result", or, even better, just set the "dragSpeed" to the maximum available of 65535.
Of note is that if you enter a negative value as "dragSpeed", which is also out of range, it is just ignored, which means it has inconsistent out of range results.
In neither failure case is anything posted to "the result".
Discovered in 7.0.3 Community, Win7 x64.
Walt
DragSpeed Failure Mode
Moderator: Klaus
DragSpeed Failure Mode
Walt Brown
Omnis traductor traditor
Omnis traductor traditor
-
- VIP Livecode Opensource Backer
- Posts: 10045
- Joined: Sat Apr 08, 2006 7:05 am
- Contact:
Re: DragSpeed Failure Mode
I agree with your assessment. I'd suggest filing an enhancement request report on that.
Richard Gaskin
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn
Re: DragSpeed Failure Mode
Walt Brown
Omnis traductor traditor
Omnis traductor traditor