George Staikos doth sayeth in a message unto Mark Kimes:

GS>   I need to know WHAT the item is that's being dropped.  I
GS> know that mp2   during CN_DROP contains a pointer to a drag
GS> buffer, but I can't transfer   the RECORDCORE in that to a
GS> RECORDCORE to be inserted into the container.

  Couple of things.. First, cruise around on some of the better OS/2 BBS's
and find a file called CNRADV.ZIP. It has some fairly decent examples of
drag and drop using containers. It doesn't go into rendering, but you'll
get enough from it to be able to handle rendering on your own.

  Second, the CN_DROP message passes a pointer to a CNRDRAGINFO structure
in mp2. The pRecord member of the structure is the record (or container
item) being dropped _on_. If the value in the pRecord member is NULL the
item(s) were dropped on whitespace in the container. So basically all it
does is give you a reference point inside your container for where the
items being dropped should be inserted.

  The pDragInfo member from the CNRDRAGINFO structure is a pointer to a
DRAGINFO structure. This is where you find out _what_ is being dropped. The
cdinfo member of this structure tells you the number of items being
dropped. Once you get that you just go into a loop calling
DrgQueryDragitemPtr() for each item being dropped. DrgQueryDragitemPtr()
returns a pointer to a DRAGITEM structure, which is the information about
an item that is being dropped on your container.

  This is about as much detail as I can go into here, if you want more
let's take this to netmail. The file I mentioned above goes into this
pretty well.

 See ya,

Craig
cam{at}wpc.cioe.com

... Windows: Brought to you by the makers of Edlin!

--- timEd/2-B9