🚀 go-pugleaf

In article <18AUG199203332039@acad3.alaska.edu>, sxmlk@acad3.alaska.edu (KIENENBERGER MIKE L) writes...
>In article <1992Aug17.104453.11070@monu6.cc.monash.edu.au>, ede978e@monu6.cc.monash.edu.au (Robert D. Nicholson) writes...
>>I have to implement Drag and Drop behaviour in NS2.1, but I would also like
>>to know wether NS3.0 can do it properly. (Look forward to reading the
>>article on it simson)
>> 
>>OK, I would like to know wether drag and drop can be implemented such that
>>the application can determine specifically which window is under the cursor.
>>ie. if there are overlapping windows, I must be able to tell which is at the
>>top. ie. above all the rest
>> 
>>Anybody done this?
> 
>Yes! (Finally.)
>The key is the little-known postscript operator "findwindow."
>	<x> <y> <place> <otherwindow> findwindow <x'> <y'> <window> <bool>
>(If you're planning on writing your own routine, note that <otherwindow>
> is a local window, while <window> is a global window! If it seems inconsistant
> to you, you are not alone!)
[example deleted]

For those who are wondering why this is necessary (since when using built-in
NeXT icon-dragging routines, the proper window is identified), the real issue
being discussed is dragging/dropping inner-app objects (palette objects, for
example).  This is the missing code for the AppkitDragView class used
in WhatADrag and other NextDeveloper examples. 
=============================================================================
-Mike Kienenberger                       SXMLK@ALASKA           (BITNet)
 University of Alaska Computer Network   SXMLK@acad3.alaska.edu (Internet)
 University of Alaska-Fairbanks