Hi Jay, > > Great, as far as the MsgWaitForMultipleObjects goes, we can set the timeout > to INFINITE if the main loop is working right, right? > I think it's 1 now because it was broke and the timeout was the only reason > the loop spun. >
Yes, we should set the timeout to a higher value. In my patch I used 10ms, because I was not sure about the reason for the 1ms. I would suggest using 1000ms, that will not consume CPU time, but is a fallback in case something totally goes wrong, to avoid that the whole application is hanging. I have just tested with 1000ms and it works fine. Gerald > Jay > > > That's the same what my patch has done, if it would have gone thru the > mailing list. > > > > Anyway, it's fixed :-) ------------------------------------------------------------------------------ Got visibility? Most devs has no idea what their production app looks like. Find out how fast your code is with AppDynamics Lite. http://ad.doubleclick.net/clk;262219671;13503038;y? http://info.appdynamics.com/FreeJavaPerformanceDownload.html _______________________________________________ Freerdp-devel mailing list Freerdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel
