How to drag n drop in a report control

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic


   

I was trying to do a simple drag n drop in a report control, but I had to reverse engineer the report control code to understand what's done, how to work with it, discover notifications messages, structures and their use. 

An example :
- There is no mention of XTP_NM_REPORT_DRAGOVER aside the XTP_NM_REPORT_BEGINDRAG, XTP_NM_REPORT_DROP or XTP_NM_REPORT_HASVALIDDROPTYPE. 
- XTP_NM_REPORT_HASVALIDDROPTYPE is commented as to be "Indicates the user dropped records to report control." This is false, this is not what is it.
- The #define DROPEFFECT_CANCEL   (5) in file XTPCustomizeTools.h f**k up the value that should be set in XTP_NM_REPORTDRAGDROP in XTP_NM_REPORT_DRAGOVER notification to forbid the drop. We have to return 0 instead of using the define DROPEFFECT_CANCEL which is so badly redefined.

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
apautrot Members Profile Send Private Message Find Members Posts Add to Buddy List Groupie Joined: 16 April 2009 Location: France Status: Offline Points: 18	Post Options Post Reply Quote apautrot Report Post Thanks(0) Quote Reply Topic: How to drag n drop in a report control Posted: 05 January 2012 at 5:37am
	I was trying to do a simple drag n drop in a report control, but I had to reverse engineer the report control code to understand what's done, how to work with it, discover notifications messages, structures and their use. An example : - There is no mention of XTP_NM_REPORT_DRAGOVER aside the XTP_NM_REPORT_BEGINDRAG, XTP_NM_REPORT_DROP or XTP_NM_REPORT_HASVALIDDROPTYPE. - XTP_NM_REPORT_HASVALIDDROPTYPE is commented as to be "Indicates the user dropped records to report control." This is false, this is not what is it. - The #define DROPEFFECT_CANCEL (5) in file XTPCustomizeTools.h f**k up the value that should be set in XTP_NM_REPORTDRAGDROP in XTP_NM_REPORT_DRAGOVER notification to forbid the drop. We have to return 0 instead of using the define DROPEFFECT_CANCEL which is so badly redefined.