korp@TRIPOLI.EES.ANL.GOV (11/11/89)
There appears to be a nasty bug in X11/NeWS. If you setcanvas to some canvas, translate, create a path and then attempt to fill the path, the whole canvas gets filled. Stroke also is affected, but not as often as fill. Several programs seem to fail with this bug. Is there a workaround? When will this be fixed. I use a 4/260 with 110Mb of swap space, when I ask for a retained canvas that is 900x900 I don't get it. I know asking for a retained canvas is only supposed to be a hint, but my machine has more than enough space to store this canvas. How does the X11/NeWS server decide when to grant retained canvases? Peter Argonne National Laboratory korp@athens.ees.anl.gov
rxb@ASC.SLB.COM (Rafael Bracho) (11/12/89)
Regarding your comment: >There appears to be a nasty bug in X11/NeWS. If you setcanvas to >some canvas, translate, create a path and then attempt to fill the >path, the whole canvas gets filled. Stroke also is affected, but >not as often as fill. Several programs seem to fail with this bug. I'm probably confused but the following code works just as you expect under X11/NeWS (my input is marked with '>'): plutionium- psh >executive Welcome to X11/NeWS Version 1.0 >framebuffer newcanvas >gsave >framebuffer setcanvas >50 50 translate >0 0 100 100 rectpath >dup reshapecanvas >stack canvas(0x491ad0,100x100,unmapped) >grestore >setcanvas >currentcanvas /Mapped true put >black setcolor >0 0 100 100 rectpath fill >white setcolor >20 20 translate >0 0 30 30 rectpath fill >currentcanvas /Mapped false put >grestore >quit psh: NeWS server disconnected plutonium- Am I missing something? Rafael Bracho rxb@asc.slb.com