Hey Koen, thanks! I'm trying to get deferRendering() and resumeRendering() up and running. The behaviour I am seeing is crash and burn :-).I am handling the initial internalPath (the one through the environment) by calling the same slot upon construction.
Calling deferRendering() from WApplication::initialize() (or from the ctor) is causing a segfault. Am I not supposed to be calling deferRendering() from either the ctor or initialize()? Thanks, Rutger On 2013-07-24 23:26, Koen Deforche wrote: > Hey Rutger, > > That really sounds like the standard use case for deferRendering() and > resumeRendering(). What behavior are you seeing when you use these > calls? > > See also here for how it's used in combination with the asynchronous > HTTP client: > http://www.webtoolkit.eu/wt/doc/reference/html/classWt_1_1Http_1_1Client.html > > You still need to take the updateLock or post() to the application for > the 'deferred' part that touches the widget hierarchy and calls > resumeRendering(). > > Koen > ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ witty-interest mailing list witty-interest@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/witty-interest
