|
|
Post by xabdullahx on Feb 3, 2016 20:27:15 GMT
This is for better app usability: 1. When we click notification "Ankulua service is running" - Please let it go to the app.. this way its easier to stop service. Script: 2. If it doesn't exist: please add an Exit or Finish command to stop the script 3. Please change vibrate(seconds) to vibrate(milliseconds) - So it looks more like android native vibrate function: developer.android.com/reference/android/os/Vibrator.html#vibrate(long) |
|
|
|
Post by AnkuLua on Feb 4, 2016 12:55:33 GMT
This is for better app usability: 1. When we click notification "Ankulua service is running" - Please let it go to the app.. this way its easier to stop service. Script: 2. If it doesn't exist: please add an Exit or Finish command to stop the script 3. Please change vibrate(seconds) to vibrate(milliseconds) - So it looks more like android native vibrate function: developer.android.com/reference/android/os/Vibrator.html#vibrate(long)1. Thanks. Will consider it. 2. Will consider it. 3. All of AnkuLua user related functions are in seconds. And most users don't know the details of Android methods. Therefore, we will keep the current way. |
|
|
|
Post by xabdullahx on Feb 4, 2016 13:26:44 GMT
3. Just because it's this way in sikuli script doesn't mean that it's the best way for this exact function. Don't forget that this is an android specific function. And there's a reason as of to why it's better to use milliseconds instead.. And that's because you rarely go above 1000 ms.. 1 seconds vibration is actually a long time, most of the times, you would use a pattern, like vibrate 200 ms, stop for 100, then vibrate again for 200.
|
|
|
|
Post by AnkuLua on Feb 4, 2016 13:58:15 GMT
3. Just because it's this way in sikuli script doesn't mean that it's the best way for this exact function. Don't forget that this is an android specific function. And there's a reason as of to why it's better to use milliseconds instead.. And that's because you rarely go above 1000 ms.. 1 seconds vibration is actually a long time, most of the times, you would use a pattern, like vibrate 200 ms, stop for 100, then vibrate again for 200. You can use vibrate(0.2) for 200ms. There is also compatibility issues with scripts already developed. Thanks for your understanding. |
|
|
|
Post by botmaker on Feb 7, 2016 2:21:04 GMT
Can we please add in next release ::
1) another api for Region:text(), which primarily will read text/numbers on the image which pops up. This is already supported under sikuli, it will be great to have this.
usage under sikuli:
reg = Region(0,0,100,100)
r = reg.text() // extracts any text from the image in that region using OCR.
2) Provide multi-touch functionality to touch apis - touchDown(PSMRL, (firstFinger=0/secondFinger=1..so on), seconds) , same for touchMove, touchUp <which finger to move up>, similar functionality exists in hiromacro/autotouch, will be really good to have here.
Thanks!
|
|
|
|
Post by AnkuLua on Feb 11, 2016 4:03:18 GMT
Can we please add in next release :: 1) another api for Region:text(), which primarily will read text/numbers on the image which pops up. This is already supported under sikuli, it will be great to have this. usage under sikuli: reg = Region(0,0,100,100) r = reg.text() // extracts any text from the image in that region using OCR. 2) Provide multi-touch functionality to touch apis - touchDown(PSMRL, (firstFinger=0/secondFinger=1..so on), seconds) , same for touchMove, touchUp <which finger to move up>, similar functionality exists in hiromacro/autotouch, will be really good to have here. Thanks! Thanks for the suggestions. Will study them. |
|
|
|
Post by zpt on Feb 19, 2016 21:43:59 GMT
Is it possible to add functions to get info about battery charge and charging state?
|
|
|
|
Post by AnkuLua on Feb 20, 2016 1:24:35 GMT
Is it possible to add functions to get info about battery charge and charging state? Will consider it. So many things to do. If the purpose is to leave the script if battery low. It may be better to reduce the power. Try setScanInterval() or insert wait in proper places in your script. |
|
|
|
Post by xabdullahx on Feb 23, 2016 13:56:47 GMT
If getChargingState were implemented, you could do:
if (getChargingState == IsCharging) then
setScanInterval(something)
else
setScanInterval(somethingElse)
|
|
|
|
Post by AnkuLua on Feb 23, 2016 14:07:00 GMT
If getChargingState were implemented, you could do: if (getChargingState == IsCharging) then setScanInterval(something) else setScanInterval(somethingElse) Will do it. |
|
|
|
Post by zpt on Feb 23, 2016 22:07:54 GMT
Also it would be usefull if there were any way to override saved settings for checkboxes and radiorgoups in dialog windows (ideally if individually for every item).
For example for the side option, which need only once. I have several of such in my script and keep forgetting to switch off their checkboxes again at the next start after use.
|
|
|
|
Post by AnkuLua on Mar 5, 2016 11:27:30 GMT
Version 5.1.0 have following new functions.
- chargerConnected()
- removePreference()
|
|
