Patches applied this morning, thanks! On Sun, Mar 18, 2012 at 3:01 PM, Felipe Astroza <[email protected]> wrote: > > Time strings are build in clock worker thread every one second. The issue > doing that is while the string is being built, another worker thread could > use this unfinished string. Example: > We have: > [16/Mar/2012 23:59:59 -0300] > An unfinished string could be like: > [17/Mar/2012 23:59:59 -0300] > And that is bad!. > My approach to the solution is to have two buffers, like double screen > buffers to avoid glitches, but applied to time strings. So, there is no > half-way string. > > Signed-off-by: Felipe Astroza <[email protected]> > --- > src/mk_clock.c | 67 ++++++++++++++++++++++++++++++++++++------------------- > 1 files changed, 44 insertions(+), 23 deletions(-) > > > _______________________________________________ > Monkey mailing list > [email protected] > http://lists.monkey-project.com/listinfo/monkey >
-- Eduardo Silva http://edsiper.linuxchile.cl http://www.monkey-project.com _______________________________________________ Monkey mailing list [email protected] http://lists.monkey-project.com/listinfo/monkey
