Path: utzoo!attcan!uunet!mcsun!ukc!stl!dr From: dr@stl.stc.co.uk (David Rutter) Newsgroups: comp.sys.apollo Subject: Re: Patch tapes; security; getpwnam; APRs Message-ID: <3104@stl.stc.co.uk> Date: 11 Jun 90 14:34:47 GMT References: <2803@syma.sussex.ac.uk> <1990Jun7.073655.20620@metro.ucc.su.OZ.AU> <1990Jun7.123032.485@bnrgate.bnr.ca> <1990Jun7.170336.19246@terminator.cc.umich.edu> Sender: news@stl.stc.co.uk Reply-To: "David Rutter" Organization: STC Technology Limited, London Road, Harlow, Essex, UK Lines: 27 > Just to be fair, I should point out that it was a pretty low > priority (plot(1) command doesn't work). > I phoned the UK response centre a month or two ago and got a quick reply on the plot bug that occurs when running plot in an Apollo window: 'plot -Tapollo'. On a bsd4.3 system 'plot' looks in /sys5.3/usr/lib rather than /bsd4.3/usr/lib. Creating a link (amongst other methods) gets it working fine. However Apollo have been very slow in another bug I found concerning DIALOG and GMR. The Dialog manual states that locator_update events are sent to graphical applications which request locator information. However under 10.1 Dialog appears to be sending locator events instead. The effect of this is that when rubberbanding graphical objects, the objects dont keep up with the cursor. It is even possible for the input buffer to overflow, crashing the program. Apollos gm_draw in the Dialog domain_examples exhibits this rubberbanding delay. Has anyone else come across this problem?