Yet another update: > > 3. One of my applications doesn't correctly update its windows. It draws a > > picture and then a crosshatch above it and a small figure that can be moved > > together with the crosshatch. Moving down works fine while moving up/left > > leaves old crosshatch marks on the screen. > That seems to be a real bug. The picture is set by calling ggiPutPixel, > while the crosshatch is drawn using ggiDrawHLine and VLine. > The Fun Thing is, that when I turn off the crosshatch everything is fine. > When turning it back on, everything below the HLine stops updating - the > VLine as well as the PutPixels.
This goes away, if I use either -noaccel or -nobuffer. > Another issue is seen when running a multithreaded part of the app: > A visual is written to by two threads, each one calling > ggiFlushRegion(state.visrender,0,y,rarg->w,1); > for each line the thread has rendered. > Funnily I test on a single-proceessor system, and I observe that only the > _SECOND_ thread I start sometimes (about 1/3rd of the lines) fails to > update the line. This goes away, if I use -nobuffer, but will stay when using -noaccel. CU, Andy -- = Andreas Beck | Email : <[EMAIL PROTECTED]> =
