{"id":105212,"date":"2021-05-13T07:00:00","date_gmt":"2021-05-13T14:00:00","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/oldnewthing\/?p=105212"},"modified":"2021-05-13T06:16:38","modified_gmt":"2021-05-13T13:16:38","slug":"20210513-00","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/oldnewthing\/20210513-00\/?p=105212\/","title":{"rendered":"Drag\/drop effects: The little drop information box"},"content":{"rendered":"

Explorer’s drag\/drop effects include a little message information box as part of the drop effect. For example, it will start with the message Move to \u2e22folder\u2e25<\/i>, but if you hold the Ctrl<\/kbd> key, the message changes to Copy to \u2e22folder\u2e25<\/i>. How can you get a piece of that action?<\/p>\n

As we saw last time, the visual drag\/drop feedback effects used by Explorer are available for general use<\/a>, via an object know as the shell drop target helper.<\/p>\n

Let’s take our scratch program and teach it how to add the fancy information box.<\/p>\n

The information box is configured by the DROP\u00adDESCRIPTION<\/code> structure which is associated with the CFSTR_DROP\u00adDESCRIPTION<\/code> clipboard format.<\/p>\n

#include <strsafe.h>\r\n\r\nHRESULT SetDropDescription(\r\n    IDataObject* dataObject, DROPIMAGETYPE type,\r\n    PCWSTR message = nullptr, PCWSTR insert = nullptr)\r\n{\r\n    wil::unique_hglobal_ptr<DROPDESCRIPTION> data(\r\n        reinterpret_cast<DROPDESCRIPTION*>(\r\n            GlobalAlloc(GPTR, sizeof(DROPDESCRIPTION))));\r\n    RETURN_IF_NULL_ALLOC(data);\r\n    data->type = type;\r\n    RETURN_IF_FAILED(StringCchCopyEx(data->szMessage, ARRAYSIZE(data->szMessage),\r\n        message, nullptr, nullptr, STRSAFE_IGNORE_NULLS));\r\n    RETURN_IF_FAILED(StringCchCopyEx(data->szInsert, ARRAYSIZE(data->szInsert),\r\n        insert, nullptr, nullptr, STRSAFE_IGNORE_NULLS));\r\n    FORMATETC fmte = { (CLIPFORMAT)RegisterClipboardFormat(CFSTR_DROPDESCRIPTION),\r\n        nullptr, DVASPECT_CONTENT, -1, TYMED_HGLOBAL };\r\n    STGMEDIUM med = { TYMED_HGLOBAL };\r\n    med.hGlobal = data.get();\r\n    RETURN_IF_FAILED(dataObject->SetData(&fmte, &med, true));\r\n    data.release();\r\n    return S_OK;\r\n}\r\n<\/pre>\n
We allocate a DROP\u00adDESCRIPTION<\/code> structure as an HGLOBAL<\/code> and copy the drop image type, optional message, and optional message insertion into the structure before setting the data into the data object.<\/p>\n
You can read the documentation for DROP\u00adDESCRIPTION<\/code> for details on how the message and message insertion interact. For this example, we’ll just use a simple message with no insertions.<\/p>\n
struct SimpleDropTarget\r\n{\r\n    ...\r\n\r\n    STDMETHOD DragLeave()\r\n    {\r\n        if (dto) SetDropDescription(dto.get(), DROPIMAGE_INVALID);<\/span>\r\n        dto = nullptr;\r\n        return helper->DragLeave();\r\n    }\r\n\r\n\r\n    HRESULT CalculateFeedback(\r\n        DWORD grfKeyState,\r\n        DWORD* pdwEffect)\r\n    {\r\n        if (grfKeyState & MK_CONTROL) {\r\n            *pdwEffect = DROPEFFECT_COPY;\r\n            SetDropDescription(dto.get(), DROPIMAGE_COPY,\r\n                L\"Copy with awesomesauce.\");<\/span>\r\n        }\r\n        else {\r\n            *pdwEffect = DROPEFFECT_MOVE;\r\n            SetDropDescription(dto.get(), DROPIMAGE_MOVE,\r\n                L\"Move with awesomesauce.\");<\/span>\r\n        }\r\n        return S_OK;\r\n    }\r\n\r\n};\r\n<\/pre>\n
When we calculate the feedback, we also set the drop description to tell the user what will happen when the drop happens. We also clear the drop description (by setting it to “invalid” with an empty message)\u00b9 when the user decided not to drop it onto our drop target after all. This ensures that our custom description doesn’t hang around and accidentally get shown for other drop targets that don’t set a description.<\/p>\n
So there you have it, drag feedback done the same way that Explorer does it.<\/p>\n
\u00b9 There is no way to remove data from a data object, so the best you can do is replace the data with new data that says “Nevermind.”<\/p>\n","protected":false},"excerpt":{"rendered":"
Updating the description.<\/p>\n","protected":false},"author":1069,"featured_media":111744,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[25],"class_list":["post-105212","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-oldnewthing","tag-code"],"acf":[],"blog_post_summary":"
Updating the description.<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/105212","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/users\/1069"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/comments?post=105212"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/105212\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/media\/111744"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/media?parent=105212"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/categories?post=105212"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/tags?post=105212"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}