MobileRead Forums - View Single Post - To programmers: help for a little "battery Report" app improvement

knc1 · 09-18-2013, 04:39 AM

And what you want displayed is the output of:

Code:

gasgauge-info -c

perhaps with some leading and/or trailing text.

I think that Amazon's gasgauge-info script already munges the percentage sign into the numeric string on all firmware versions,
If so, then

Code:

eips 1, 2 `gasgauge-info -c`

With changes in the x, y starting position of your choice should 'just work'.
Note: Those are back-ticks, not single quotes.

And since it is a single command, you don't need a bin/shell-script.sh to get it done, just put it as the 'action: ' in the menu.json of your new button.
(Unless the version-2 KUAL parser broke that feature. The version-2 parser is a bit annal in the things it will accept.)

09-18-2013, 04:39 AM	#7
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	And what you want displayed is the output of: Code: gasgauge-info -c perhaps with some leading and/or trailing text. I think that Amazon's gasgauge-info script already munges the percentage sign into the numeric string on all firmware versions, If so, then Code: eips 1, 2 `gasgauge-info -c` With changes in the x, y starting position of your choice should 'just work'. Note: Those are back-ticks, not single quotes. And since it is a single command, you don't need a bin/shell-script.sh to get it done, just put it as the 'action: ' in the menu.json of your new button. (Unless the version-2 KUAL parser broke that feature. The version-2 parser is a bit annal in the things it will accept.) Last edited by knc1; 09-18-2013 at 04:53 AM.