Path: utzoo!attcan!uunet!husc6!bbn!uwmcsd1!ig!agate!ucbvax!CORY.BERKELEY.EDU!dillon From: dillon@CORY.BERKELEY.EDU (Matt Dillon) Newsgroups: comp.sys.amiga Subject: Re: Dmouse and PATH (was Re: POPcli bug? (was Re: ConMan Question)) Message-ID: <8807050651.AA20133@cory.Berkeley.EDU> Date: 5 Jul 88 06:51:08 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 31 >I have only one disk drive, and REZ a batch of commands so that I don't have to >keep my startup disk around all the time. One of those commands is "newcli". >If I am forced to use a "from" file to get the PATH set correctly, I will have >to swap disks every time I want a new CLI. > >Perhaps Matt could possibly fix this problem in 1.08? Problem: How? Dmouse's process does not have a CLI so how does Execute() know where to get the path from? In your case, you could simply put the script in RAM: or something, no? >One very tiny problem with Dmouse 1.07: > >The pointer is automatically blanked when the screen is blanked irregardless of >whether or not mouse blanking is enabled. However, when mouse blanking is >disabled, the mouse pointer does not reactivate along with the display on a >keypress. It does reactivate with the display on a mouse movement. Ahhh ... right, because you have mouse blanking disabled it *should* turn back on when the screen is unblanked. By the way, as per somebody's suggestion I am now using UpFrontLayer() etc... instead of the intuition WindowToFront() etc... calls, which appears to fix all instances of lockup with workbench icons. It will be in 1.08 (but so far that's the only thing I've added since 1.07, so I'm not releasing 1.08 yet). -Matt