win32cpp eventually needs at least one, and likely two drag and drop
implementations. On IRC we discussed "internal" vs "external" drag and
drop, and agreed that both implementations are likely necessary.
"Internal" drag and drop refers to all drag and drop operations handled
within a single win32cpp application instance. This will likely include
homebrew mouse handling, drag sources, and drop targets.
"External" drag and drop refers to drag and drop communication with other
applications (e.g. Windows Explorer), and will likely need to be
implemented with OLE.
Original issue reported on code.google.com by casey.la...@gmail.com on 9 Sep 2008 at 9:04
Original issue reported on code.google.com by
casey.la...@gmail.com
on 9 Sep 2008 at 9:04