dialog - ELF binary - Parameter for no buttons?

[neil_swann80]

I've been playing with the built-in "dialog" binary:
/ebrmain/cramfs/bin/dialog

I understand that a message box can be called via:

dialog n "title" "message" "b1" "b2" "b3"

The button pressed assigns 1, 2 or 3 to the variable $?

Where n determines an icon to be shown by choosing 1-5:

1. i - info icon
2. ? - questionmark icon
3. ! - exclamation mark icon
4. X - error icon
5. WIFI icon

Any number that's not 1-5 will not display an icon.

I'm not sure what the title field does, as entering anything here isn't displayed on the message box itself. My guess is that it's a title for the individual message box process?

The message field is self-explanatory and no problems there.

You can display up to 3 buttons. BUT even if you don't specify any buttons at all (blank line after message) if defaults to a single button. I'm sure I have seen system apps use dialog messages without a button, so I'm thinking there must be a parameter for this? Does anybody know what it might be, or how I could find out? I've examined the ELF binary via a hex editor and via dumpelf but haven't been able to glean any insight.

EDIT:
rkomar pointed me in the right direction, the dialog binary uses the "dialog" inkview function which requires at least one button. The "message" function has a timeout and no buttons.

Message (int icon, char *title, char *text, int timeout)

Dialog (int icon, char *title, char *text, char *button1, char *button2, iv_dialoghandler hproc)

[rkomar]

How do you make it go away if you don't have a button to click? Typically, you provide a timeout value if you don't want any buttons, but you aren't showing any option for that above.

Edit: Besides, a "dialog" means some kind of interaction. What you are thinking of is a "message", which typically has a timeout value to make it disappear on its own.

[neil_swann80]

Either a timeout or the entire message box itself becomes a clickable ok/cancel button.

When you mentioned the strange functions associated with the "iv2sh" binary (regarding the reboot command), how did you view those functions? (ah, just calling it in terminal spits out the functions.)

If there is a timeout function, is there a way to find the parameter that initiates it from the binary? And any other valid parameters?

[rkomar]

I don't think there is a timeout parameter. The help information just displays the Dialog functions from the Inkview API that are called inside the program. Neither takes a timeout argument because dialogs require an answer of some kind, so they will wait forever until they get one.

If you want to display a message and go away after a timeout, I think you will have write your own program that calls the Inkview API Message() function. I glanced through the programs on my Colour, and I don't see anything that obviously does that already.

[neil_swann80]

Yep, of course you're correct about the Inkview API Message() function.

I'll have a crack at writing a simple program.
https://github.com/dennwc/inkview
This suggests that a program compiled in GO shouldn't even require the SDK.

On a different note, do you happen to know where the browser.app cookies are stored?

[rkomar]

Originally Posted by neil_swann80

On a different note, do you happen to know where the browser.app cookies are stored?

No, I have never looked for them. Most things are stored somewhere in the /system/ directory, so you should be able to find them there. That part of the file system is accessible over UMS, so you can look for it with your desktop software if you mount the filesystem over USB.

[neil_swann80]

Found it!

SQLite file: /mnt/ext1/system/state/storage/browser/cookies

I was hoping for a simple text file.

Editing this on the device itself could be tricky. I'm sure I saw a post somewhere that showed python working on Pocketbook devices. Perhaps I can get PySQLite working.