-
John,
I think your e-mail is well and truly up S**T creek! :p
I've been trying to send stuff for a week...last resort I'm posting here...
You've quite possibly seen all this already, but just in case...
:cool:
Dan
____________________________________________
____________________________________________
John,
I attempted to send the message below to both your e-mail addresses last week.
I had problems with both and I'm not sure if you got either, so I'm resending.
Apologies if you've got this already.
Regards,
Dan
*******************************************************************************************
John,
Using 4 bytes works (I think) because you've already DIMmed a receiving object that 'knows'
how big it is, you just have to tell it where to start using a 4 byte pointer. As far as
why the TreeView thing will 'never' work read Stevie-O's explanation at:
http://forums.vb-world.net/showthrea...threadid=15806
Still, I'd like to know how drag and drop works to 'copy' objects....
Dan
-
Wow, my name in lights!
OK, my mail server works now, it's been down for a week.
After you emailed me, I realized that a 32-bit pointer is 4-bytes which is of course why you use 4 bytes for copyMem.
Anyway, Stevie-O sounds reasonable. The dragdrop in the MSDN example works because all of the nodes are already in the collection, the code just changes the .parent pointer of the dragged node. Even if we added an extra reference to the nodes with CopyMem like he says, shouldn't it work at least until the collection is destroyed? (The memory location is still valid to that point...)
I thought you'd given up on this (or solved it) b/c I hadn't heard from you. :)
-
To be honest....
....I have more or less given up on the idea. It seems that even if it is possible its:
a). too much hassle to figure out and
b). not flexible enough anyway.
I've nothing against you keeping at it though :p
:cool:
Dan
