Hey Pau, 2008/9/11 Pau Garcia i Quiles <[EMAIL PROTECTED]>: > In this case I only needed it to work server-side.
I am not sure what you mean by that, but as long as the result of a timeout may reflect in a change in the UI, it really needs to be triggered from the browser, unless you have server-side updates. >> This should always work though, unless you are blocking the event loop >> and try to use it while handling a single event ? > > I'd say I'm not blocking it: > http://websvn.kde.org/trunk/playground/office/elampo/wtstrigiclient.cpp?view=markup > > (the timer is called "poller") That code seems fine. It does not work, at all ? Not even the first timeout gets through ? That is very weird. Did you check on the raw access_log (assuming you run using the built-in httpd) ? 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
