Ambiguous API for waiting (milliseconds or seconds?)
Bug #516377 reported by
UNV
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| SikuliX |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Currently API doesn't decide whether it wants to describe time in milliseconds (wait function) or seconds (sleep function).
From user perspective seconds are more preferable (almost all UI intervals are measured in seconds, millisecond can be easily specified as 0.001). Nevertheless all API functions should use the same time measurement unit.
By the way, why do you need special sleep() function? From my point of view, wait(<number>) should have the same semantics.
Revision history for this message
| Tsung-Hsiang Chang (vgod) wrote | #1 |
| Changed in sikuli: | |
| status: | New → In Progress |
| tags: | added: 0.10 |
| Changed in sikuli: | |
| milestone: | none → 0.10.0 |
Revision history for this message
| RaiMan (raimund-hocke) wrote | #2 |
| Changed in sikuli: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
This will be fixed in the 0.10 release.