Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!uflorida!gatech!udel!mmdf From: kevin%amdahl.uts.amdahl.com@UDEL.EDU Newsgroups: comp.sys.amiga Subject: Re: following the sliding prop gadget Message-ID: <4381@louie.udel.EDU> Date: 3 Oct 88 21:55:12 GMT Sender: mmdf@udel.EDU Lines: 65 Received: from CUNYVM by CUNYVM.BITNET (Mailer X2.00) with BSMTP id 2833; Fri, 30 Sep 88 16:51:37 EDT Received: from UDEL.EDU by CUNYVM.CUNY.EDU (IBM VM SMTP R1.1) with TCP; Fri, 30 Sep 88 16:51:33 EDT Received: by Louie.UDEL.EDU id ad10648; 30 Sep 88 13:00 EDT Received: from Louie.UDEL.EDU by Louie.UDEL.EDU id ad10283; 30 Sep 88 12:28 EDT Received: from USENET by Louie.UDEL.EDU id aa10213; 30 Sep 88 12:25 EDT From: Kevin Clague Subject: Re: following the sliding prop gadget Message-ID: Date: 30 Sep 88 15:37:21 GMT Organization: Amdahl Corporation, Sunnyvale, CA 94086 To: amiga-relay@UDEL.EDU Sender: amiga-relay-request@UDEL.EDU In article <9515@cup.portal.com> Sullivan@cup.portal.com writes: >> >>I would like to see the contents of one of my windows scroll continouously >>as I slide a prop gadget up and down, rather than just get one change >>when I finish let go of the select button. Preferences and Manx's SDB > >Sounds like your gadgets are changing the screen (as well they should) but >since Intuition now has a lock on the front bitmap (to animate the gadget) >nothing else in the window can update. more untruths about Intuition and gadgets deleted.... Intuition does not keep any lock on the window (or any of it's parts) for long periods of time like that. The problem is that you aren't getting the messages when you expect them. You must not have your window or gadget set up properly. When you want to get mousemoves from a gadget, you must make sure the gadget AND the window's IDCMP stuff is set up properly. All this is from memory (boy I need to get some RKM's for work, or Net access at home)... To set things up: 1. Set up the FOLLOWMOUSE and GADGIMMEDIATE flags. You can set RELVERIFY if you want to stop getting MOUSEMOVES when the mouse is outside the potentiometer's container. If you have IDCMP set up properly, this should give you GADGETDOWN, MOUSEMOVES, and GADGETUP messages. 2. In the window, you must make sure the window flags and IDCMPFlags are set up properly. Make sure your NewWindow structure's Flags member has REPORTMOUSE set in it. If your program always wants to see MOUSEMOVES, you should set the MOUSEMOVES flag in the NewWindow structure's IDCMPFlags. If you normally have your IDCMP set up to not receive MOUSEMOVES then when the user presses the potentiometer gadget, you should start to receive MOUSEMOVE message. They should stop once the user releases the mouse button (or go out of the potentiometer container and you have RELVERIFY set.) This is a long winded explanantion, but Sullivan seemed so far off base that I felt I should try to correct things. There is absolutely no need to go directly to the screen to do any rendering or simulate your own gadget stuff. Tom Skrobala (the original author) seemed to be getting mouse moves, but without more information, it's hard to know if they are associated with the potentiometer gadget, or just the window.