Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!ll-xn!ames!amdahl!kim From: kim@amdahl.amdahl.com (Kim DeVaughn) Newsgroups: comp.sys.amiga Subject: Re: ClickToFront executable (and random ramblings) Message-ID: <9081@amdahl.amdahl.com> Date: Mon, 22-Jun-87 16:57:29 EDT Article-I.D.: amdahl.9081 Posted: Mon Jun 22 16:57:29 1987 Date-Received: Tue, 23-Jun-87 05:32:36 EDT References: <8706221319.AA12365@cogsci.berkeley.edu> Organization: Amdahl Corporation, Sunnyvale, CA 94086 Lines: 93 In article <8706221319.AA12365@cogsci.berkeley.edu>, bryce@COGSCI.BERKELEY.EDU (Bryce Nesbitt) writes: > In article <>, kim@ahmdal.ahmdal.COM writes: ^^^^^^^^^^^^^^^^^ Never try getting a job as a mailer daemon Bryce, or are you gonna blame it on the lineeater? That should be amdahl.amdahl.COM ... :-) :-) :-)! > > > > Here's a warning for ClickToFront'ers ... if you have Facc, and are using > > AutoFacc, you'll have to decide if you want to use ClickToFront *or* > > AutoFacc. AutoFacc won't work properly if ClickToFront is installed, > > because of the way it (AutoFacc) "cheats", faking the mouse input. Sigh. > > Just start ClickToFront *after* autofacc. Yeah, this will work fine for the initial startup invocation of Facc (followed by AutoFacc), but doesn't help later on down the road with subsequent Facc-fiddling using AutoFacc. Actually, subsequent use will at least push the Facc window to the back, but the +/- feature won't do it's thing to the buffer count, nor will it cause the Facc window to shrink. > ClickToFront sees AutoFacc's "Mouse" movements, and responds just like > if the user had made them. I suspect (not having the sources to it) that AutoFacc fakes clicking on Facc's More and Fewer buttons once for each buffer to add/delete, instead of trying to fake "holding" the mouse button down. Since these are issued at a *very* rapid rate, ClickToFront sees them as "double-clicks" and keeps bringing the Facc window to the front over- and-over again. I think I only tried to add/delete an even number of buffers ... have to try an odd number and see if it'll still recognize the push-to-back "click". Or maybe try adjusting the double-click sensitivity in Preferences (though I think AutoFacc issues it's clicks way too fast for that to make a difference). In any case, all this is a kluge that will go away soon. In the meantime, I'll just use AutoFacc in the startup-sequence (ahead of ClickToFront) for IPL'ing the machine, and deal with Facc manually after that. > > Hmmmm ... Brown-Wagh/Micro-Systems Software is supposed to have a program > > coming out (RSN) that records mouse movements, clicks, keyboard entries, and > > such, and lets you make "macros" out of them. Wonder if there will be any > > interference with ClickToFront ... Bryce? > > ClickToFront hooks into the input.device stream at priority 51, just before > Intuition. This means it sees all real mouse events, and all fake mouse > events added by sneaky software. > If two of these are mouse down events over windows, and meet the double-click > time the current window will be poped to the front. Avoid doing that while > recording, and everything will go as planned. Even if a double-click event > is generated, it often will be harmless. Based on the above (which could well be wrong), seems like ClickToFront eats (removes from the input food chain) anything it interprets as a double-click [alas, the source is somewhere in Purdue, so I can't check]. Not a problem for most real-time playback of recorded sequences, but the MSS product I mentioned above had several playback modes ... one of which was a time-compressed mode (dat ol' mouse can really whiz around, clickin' here, clickin' there)! Seems like this could be a real problem, not to mention rapid "extended selects" and such. Would it be a problem for ClickToFront to pass the mouse events on down the line after it's done it's WindowToFront thing? > This precludes use with "SunMouse" or "AutoPoint" since these generate > fake mouse down events for EVERY KEYBOARD KEY that is pressed. Whoa ... hold on there! ClickToFront works just fine for me running jimm's AutoPoint2. I haven't tried SunMouse or MoonMouse to see what happens with them though. > Two solutions are possible: > > 2> Add "AutoPoint" to "ClickToFront", as an option. Too bad for all you > AutoPoint fans that I just don't like AutoPoint... Ah, but we do have the source, Bryce (or at least "doc" does, anyway) :-)! /kim -- UUCP: kim@amdahl.amdahl.com or: {sun,decwrl,hplabs,pyramid,ihnp4,seismo,oliveb,cbosgd}!amdahl!kim DDD: 408-746-8462 USPS: Amdahl Corp. M/S 249, 1250 E. Arques Av, Sunnyvale, CA 94086 CIS: 76535, Ba