Hi Rex,
That's odd, we are not seeing that happen here. Do you perhaps have multiple OneDrive accounts, such as work and home ones?
Could you go to the ShellTreeListBox Intro sample and do a text copy/paste in your reply of the 3 "Selected object ..." properties (at the bottom of the Sample Options list) and their values for EACH of the four OneDrive nodes? You will have to select each node, one at a time, to get that information. I'm curious what it says the differences are in parsing name, etc.
Also, the 23.1.0 version added code to try and filter out Documents and Pictures from the root Desktop parent, since Microsoft at some point in Windows 11 started including those as results. When looking at root Desktop child nodes, we specifically look at the child node shell object's SpecialFolderKind and if it is Documents, LocalDocuments, LocalPictures, Pictures, and others, we exclude it from the results.
It could be that for some reason the folders are not being recognized and labeled properly with a SpecialFolderKind, meaning they aren't getting filtered out. In addition to listing out the data requested in the above reply, it would be helpful to know what each child node's SpecialFolderKind value is.
No, I don't have multiple OneDrive accounts.
The three Selected object properties for them are here:
C:\Users\rex_h\OneDrive\Documents
Documents
C:\Users\rex_h\OneDrive\Documents
C:\Users\rex_h\OneDrive\Documents
Documents
C:\Users\rex_h\OneDrive\Documents
C:\Users\rex_h\OneDrive\Pictures
Pictures
C:\Users\rex_h\OneDrive\Pictures
C:\Users\rex_h\OneDrive\Pictures
Pictures
C:\Users\rex_h\OneDrive\Pictures
And they have these properties:
SpecialFolderKind None ActiproSoftware.Shell.SpecialFolderKind
RelativeParsingName "::{A8CDFF1C-4878-43BE-B5FD-F8091C1C60D0}" string
SpecialFolderKind None ActiproSoftware.Shell.SpecialFolderKind
RelativeParsingName "::{D3162B92-9365-467A-956B-92703ACA08AF}" string
SpecialFolderKind None ActiproSoftware.Shell.SpecialFolderKind
RelativeParsingName "::{3ADD1653-EB32-4CB0-BBD7-DFA0ABB5ACCA}" string
SpecialFolderKind None ActiproSoftware.Shell.SpecialFolderKind
RelativeParsingName "::{24AD3AD4-A569-4530-98E1-AB02F9417AA8}" string
Hi Rex,
Thank you for posting the GUIDs, that really helped. We try to identify special folders with the published known folder IDs on Microsoft's site. But it looks like in your case and perhaps others, some alternate GUIDs are being used for some of these special folders. We were able to locate a list of the alternates that I think will cover everything and prevent those four entries from showing up in the root Desktop node.
If you write our support address and mention this thread, we'll be happy to send you a preview build to test the update.
Please log in to a validated account to post comments.