My first sugesstion is to create a separate branch and try to compile it with the newest version. My second suggestion is if possible show us the error log and the code that causes the errors. Is it a segfualt? Is it a deadlock? What kind of errors are you guys getting? It doesn't work! doesn't really help us.
Omer Katz 2010/1/13 HADASS YAARI <[email protected]> > Hello everybody, > In order to accelerate updates of dynamic pages and due to your > recommendation, I changed 3 dynamic pages from updating by WTimer to > updating by server push. > I added a signal and a cyclic thread that emits it whenever needed. The 3 > pages (container widgets) connect to the signal in the Ctr. > I use the same method to update the page that I used with the Wtimer. > I don't know why but the application collapse when updating. The collapse > is not consistent and also the errors not. > > I implemented exactly like in the simpleChat example: > In the Ctr I wrote: WApplication::instance->enableUpdate(); > and also connected to the signal. > > In the method that is called by the signal emit I wrote: > lock = WApplication::instance->getUpdateLock(); > and then I clear 2 tables and inseret new data to them. > afterwards : > WApplication::instance->triggerUpdate(); > > The collapse is not when calling triggerUpdate but in the methods between > getting the lock and triggerUpdate. > > the errors are different everytime. One of the errors was from > CreateDomElement and another one from WebRender::needUpdate(). > > What's the problem? > the same methods works fine with the WTimer so I guess the problem is not > in the updating table methods. > I use older version of Wt (2.2.3) - If this bug was fixed, please tell me. > > Thank you, > Hadas > ------------------------------ > * This message (including any attachments) issued by RAFAEL- ADVANCED > DEFENSE SYSTEMS LTD. (hereinafter "RAFAEL") contains confidential > information intended for a specific individual and purpose, may constitute > information that is privileged or confidential or otherwise protected from > disclosure. If you are not the intended recipient, you should contact us > immediately and thereafter delete this message from your system. You are > hereby notified that any disclosure, copying, dissemination, distribution or > forwarding of this message, or the taking of any action based on it, is > strictly prohibited. If you have received this e-mail in error, please > notify us immediately by e-mail mailto:[email protected] and completely > delete or destroy any and all electronic or other copies of the original > message and any attachments thereof. * > ------------------------------ > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and > easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > witty-interest mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/witty-interest > >
------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
