Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!mcgill-vision!snorkelwacker!usc!zaphod.mps.ohio-state.edu!rpi!uupsi!rodan.acs.syr.edu!bwdavies
From: bwdavies@rodan.acs.syr.edu (Davies)
Newsgroups: comp.databases
Subject: Re: Mouse Support in Foxpro
Summary: Check the demo ...
Keywords: Mouse, demo, FoxPro
Message-ID: <1990Sep12.205621.9505@rodan.acs.syr.edu>
Date: 12 Sep 90 20:56:21 GMT
References: <1990Sep12.025454.16163@morrow.stanford.edu>
Sender: Sam Hill Cabal, DS
Organization: Syracuse University, Syracuse, NY
Lines: 24

In article <1990Sep12.025454.16163@morrow.stanford.edu> AR.HFN@forsythe.stanford.edu (Hooshyar Naraghi) writes:
>
>The ON KEY LABEL MOUSE is ok to use, but how can we write the code
>so that we know which object (or memory variable) was hit.  Then, we
>can construct a CASE or IF block to take different courses of action
>depending on which object was hit.
>Hooshyar Naraghi
>AR.HFN@forsythe.stanford.edu

We only have the demo at my workplace (I'm still trying to convince the 
higher-ups), but there is a section of code in the demo program that
distinguishes between different boxes when clicked on with the mouse.


-------------------------------------------------------------------------------
Sam Hill Cabal				"If there's anything insidious going
bwdavies@sunrise.bitnet			 on in the world, the media is behind
bwdavies@rodan.acs.syr.edu		 it!"	-T.J. Teru
------------------------------------------------------------------------------
--
-------------------------------------------------------------------------------
Sam Hill Cabal				"If there's anything insidious going
bwdavies@sunrise.bitnet			 on in the world, the media is behind
bwdavies@rodan.acs.syr.edu		 it!"	-T.J. Teru