Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watmath!clyde!bellcore!faline!ulysses!csw From: csw@ulysses.UUCP Newsgroups: comp.windows.news Subject: Bug in Item package? Message-ID: <3222@ulysses.homer.nj.att.com> Date: Wed, 25-Nov-87 15:29:22 EST Article-I.D.: ulysses.3222 Posted: Wed Nov 25 15:29:22 1987 Date-Received: Sun, 29-Nov-87 03:00:06 EST Organization: AT&T Bell Laboratories, Murray Hill Lines: 47 Running NeWS 1.0, using litewin.ps and liteitem.ps, whenever I try to create a ButtonItem with the FrameCanvas as parent, the window can no longer be killed. After "Zapping", the window remains drawn on the screen and stops input. If I make the ClientCanvas the parent of the item, everything works fine, but then of course I cannot position my item where I want. Included here is a sample program that exhibits the behaviour. Can anyone tell me if this is fixed in 1.1? Does anyone know a quick workaround? I have found one but it is not very pretty. ----- Chris Warth ATT Bell Laboratories Murray Hill, NJ ulysses!csw ----- systemdict /Item known not { (/usr/NeWS/lib/NeWS/liteitem.ps) run } if % % Create a window. % /win framebuffer /new DefaultWindow send def % Create a window 0 0 360 360 /reshape win send % Shape it. /map win send % Map the window. pause pause pause pause pause pause pause /items 1 dict def { items begin /nextbutton (NEXT) {} FrameCanvas % <-- replace with ClientCanvas to get it % to work. ( NEXT ) stringwidth pop BorderTop 5 sub /new ButtonItem send BorderTop 3 mul FrameHeight BorderTop sub 3 add /move 3 index send def end } win send /itemmgr items forkitems def items paintitems currentprocess waitprocess % wait for something interesting to happen. --