Hey Goetz,

2008/9/30 Goetz Babin-Ebell <[EMAIL PROTECTED]>:
>> 2008/9/30 Goetz Babin-Ebell <[EMAIL PROTECTED]>:
>> > Hello folks,
>> >
>> > I have a page displaying status information.
>> > I would like to update this status information
>> > when the user hits reload.
>> >
>> > Is there a way to do this ?
>>
>> Reimplement WApplication::refresh() any WWidget::refresh(), and make
>> sure the browser reload does not spawn a new session (which is the
>> default in wt_config.xml).
>
> * Do I really have to reimplement refresh() in every Widget I use
>  or is it sufficient to only reimplement refresh() in WApplication ?

Refresh is by default propagated by all widgets through the widget
hierarchy (even for composite and reimplemented widgets). So unless
you really want to update something, you do not need to reimplement
refresh().

In your case, assuming you have a widget for displaying status
information, only that widget needs a special refresh() method.

> * Is there a way to determine if the refresh() is a result from external
>  operation (user clicks reload) or an internal refresh() call ?

Not really. But currently refresh() is never called without an
external operation, so you should be able to deal with your calling of
refresh() in a custom way?

Regards,
koen

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
witty-interest mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/witty-interest

Reply via email to