| gerhard.petrowitsch@philips.com 2005-01-19, 4:20 pm |
| Hi all,
in case you don't find the oddities in the behaviour I described
in my previous post, you could try these things:
after startup of testScale.pl or testScale.tcl
- change -resolution to 2
-> tickinterval at the SUT also changes to 2 automatically
- change the resolution back to 1
-> tickinterval at the SUT doesn't go back to 1 and cannot be forced to
do so even with the tickinterval slider (bottommost one)
Exit and restart
- change -resolution to 5
-> tickinterval changes also to 5 automatically
- change -resolution back to 3
-> tickinterval changes back to 3 automatically, too
- change -resolution back to 2
-> tickinterval changes to 4 automatically instead of 2 and cannot be
forced back to 2 even with the tickinterval slider (bottommost one)
Exit and restart
- change -from to 1
- change -resolution to 2
-> I would expect the 'resolution grid' to be 1, 3, 5... but it's set to
2, 4, 6... automatically instead
- change -resolution to 4 then back to 2
-> -from value of the SUT is now 4 for what reason ever
Exit and restart
- change -tickinterval to 3
- change -resolution to 3
- now change -tickinterval back to 2
- move the slider of the SUT and watch the shell
-> the output values are on a grid that matches the 'tickinterval'
instead of the 'resolution' !!
Regards,
Gerhard
-++**==--++**==--++**==--++**==--++**==--++**==--++**==
This message was posted through the Stanford campus mailing list
server. If you wish to unsubscribe from this mailing list, send the
message body of "unsubscribe ptk" to majordomo@lists.stanford.edu
|