pidl | A declarative work pipeline definition language for Ruby | BPM library

If you need the full path, then combine the ParentAbsIdList and ItemRelIdList lists into a new absolute PItemIDList list:

How do I convert a relative PIDL into an absolute PIDL?

And then use SHGetPathFromIDList().

Alternatively, you can use ParentIShf.GetDisplayNameOf() instead, passing it ItemRelIdList as-is. If you specify only the SHGDN_FORPARSING flag, you will get back the child's full path. If you include the SHGDN_INFOLDER flag, you will get back the child's path relative to its parent.

The RzShellUtils unit provides utility functions for working with PItemIDLists. For instance, ConcatIdLists() (and ShellMemFree()), ShellGetPathFromIdList(), and ShellGetFriendlyNameFromIdList():

As noted in the comments above, the OnDragDrop and OnDragOver events are specifically for the VCL internal drag and drop and are not involved in the OLE Drag-and-drop processing implemented by the TRzShellTree. Further complicating things is that there are no events surfaced in the TRzShellTree's OLE Drag-and-drop processing. The method that handles the drag over functionality is virtual, but I don't think that will lead to what you want.

Another option would be to turn off the OleDrag and OleDrop settings in the Options property and use the DropMaster components to deal with the Drag-and-Drop functionality. You have a lot more control over the drag operations with DropMaster.

Actually after posting this question on their GitHub i received an answer which turned out to be the solution. You need to specify the cellNamespace for the graph and the cellViewNamespace for the paper object.

See here: https://github.com/clientIO/joint/issues/1579

Visual Studio works on the project file, which contains a whole bunch of cl and link options, whereas when you run your cl command manually you run it with different arguments. It's normal to get different results.

Also note that the error you see from your project is correct, if NumOfpidls is 0 then your program will dereference a null variable. Edit: actually you don't even initialize it, so you'll dereference garbage. That truly is terrible code.

When a PIDL only contains the name and no other information you are looking at a simple item. These are generated by SHSimpleIDListFromPath when the change notifier only knows the path or if the notifier used a empty find info in the bind context when creating the PIDL.

Your only option is to hit the disk and fill in a new PIDL. In generic shell namespace speak this means asking IShellFolder to parse the display-name. IShellItem2::Update might do this for you, the documentation does not say if it is valid for simple items.

Thanks to the comment from @IInspectable, that's the hint i needed.

Solution:
Add CoInitialize before calling GetExtractImageItfPtr and add CoUninitialize after receiving the file preview, but still within the worker thread.
Ensure that CoUninitialize is called even if exceptions occur by using try and finally`.

Working source code for main unit with worker thread:

Here is some sample code (using ATL for smart pointers) that displays all properties for all items in the recycle bin (or any other folder you'd like).

You can pick the properties you want. I've dumped a sample output with a deleted txt file. The item's display name actually depends on the maching settings, but you can see there are lots of other interesting properties, for example:

• System.Recycle.DeletedFrom (eq to SCID_RemovedFrom)
• System.Recycle.DateDeleted (eq to SCID_DateDeleted)
• System.ItemNameDisplay (note for virtual items, you won't always have a System.FileName)
• System.ItemType (note for virtual items, you won't always have a System.FileExtension)

Sample output:

This is the solution to it using FindWindowW e SetWindowPos Api. It is showing Explorer folder on top of top most form.

In the pictures below you have seen that in my program I do not view Open in program sub menu. I have only one item "Open in program".

The reason for this is that these submenus are delay-generated (which explains why they don’t contain anything interesting when you expand them) and owner-drawn.

So you need to handle messages associated with owner-drawn menu items.

After that you will get what you expected like this:

The following is an Win32 C++ sample code you can refer to: