[slezica]

Hi to everybody,
We work with Python in Nokia cellphones from a year or two. This forum and wiki is awesome, and everytime we find the answer to our cuestions before ask .
Now, in a project we find some I think standard 'alerts' or 'queries' missing from Python:

a) A simple alert who wait for a user keypress (with a soft-button 'ok' or 'accept').

b) A text-viewer like the used with the license in the installers, (with or without the link support).

Anyone know if is possible do some like this with Python, or we need to 'draw' all with TopWindow?. Is this the right thing?.

What I do for now: Using the appuifw2 (great module, thanks to the author, I like the view approach!), I use the query with soft-button labels assigned for example to 'OK' and ''. BUT... I can´t change the icon.

Is possible, hide or change the icon in a query?.

Really thanks and please excuse my english,

Sebastián Lezica
Dos al Infinito
+54 (11) 4619-1053
Buenos Aires / Argentina

[miohtama]

Originally Posted by slezica

Hi to everybody,
We work with Python in Nokia cellphones from a year or two. This forum and wiki is awesome, and everytime we find the answer to our cuestions before ask .
Now, in a project we find some I think standard 'alerts' or 'queries' missing from Python:

a) A simple alert who wait for a user keypress (with a soft-button 'ok' or 'accept').

b) A text-viewer like the used with the license in the installers, (with or without the link support).

Anyone know if is possible do some like this with Python, or we need to 'draw' all with TopWindow?. Is this the right thing?.

What I do for now: Using the appuifw2 (great module, thanks to the author, I like the view approach!), I use the query with soft-button labels assigned for example to 'OK' and ''. BUT... I can´t change the icon.

Is possible, hide or change the icon in a query?.

Check uiklduges project:

http://code.google.com/p/uikludges/

It offers some of the functionality you require.

[slezica]

Dear Mikko,
Thanks, your module is excelent!. Your query component is very handy.
Do you have any recomendation about how I can add a timer for autoclose if the user don't answer in X time?. I think in a 'poor man' solution using the ao_timer.after and simulate a keypress.

I mix your long-text with header message query with the edit label procedure of appuifw2 and work very good:

from appuifw import schedule
from _appuifw2 import command_text
import uikludges as uik

def set_ok_cancel(ok, cancel):
    try: command_text(-2, ok)
    except: pass
    try: command_text(-1, cancel)
    except: pass

schedule(set_ok_cancel, u"Yes, maybe", u"Never")
uik.query(text=u"Some text... "*10, type="message", defval=None, header=u"Title", show_left_softkey=True, tone=uik.ENoTone)

Thanks again, and please excuse my english,

Sebastián Lezica

[miohtama]

[quote=slezica;494302]Dear Mikko,
Thanks, your module is excelent!. Your query component is very handy.
Do you have any recomendation about how I can add a timer for autoclose if the user don't answer in X time?. I think in a 'poor man' solution using the ao_timer.after and simulate a keypress.
[/code]

This will work, but the proper solution would be retrofit the dialog code to have a timer or asynchronous handling. Can you suggest a particular function and where it should be added?

[slezica]

Originally Posted by miohtama

This will work, but the proper solution would be retrofit the dialog code to have a timer or asynchronous handling. Can you suggest a particular function and where it should be added?

I think the async handling is more powerful, but timeout parameter can be simple for use, and enough for most cases.

Maybe the more transparent approach (from the user side) is a module procedure like "cancel_query", who can be called from another thread (or inside a simple timer for example). If this is possible, the notes/queries keep the compatibility to the past. I feel bad because talk is easy compared to DO, I don't know how much complicated can be implement this.

I look in the svn your new addition about progress dialogs, now I'm downloading for view this. Your proyect is like the gold pot at the end of the rainbow! .

Thanks!,

Sebastián

[miohtama]

Originally Posted by slezica

I think the async handling is more powerful, but timeout parameter can be simple for use, and enough for most cases.

Maybe the more transparent approach (from the user side) is a module procedure like "cancel_query", who can be called from another thread (or inside a simple timer for example). If this is possible, the notes/queries keep the compatibility to the past. I feel bad because talk is easy compared to DO, I don't know how much complicated can be implement this.

I look in the svn your new addition about progress dialogs, now I'm downloading for view this. Your proyect is like the gold pot at the end of the rainbow! .

Thanks!,

Sebastián

Check also this:

https://launchpad.net/pys60community