New API folderitem

General
21

Sam, I understand the opposite, you get the alias itself if you pass False, and the file pointed by the alias if you pass true.
Then to replace GetFolderItem -> pass True, Get TrueFolderItem -> pass False.

22

[quote]Sam, I understand the opposite, you get the alias itself if you pass False, and the file pointed by the alias if you pass true.
Then to replace GetFolderItem -> pass True, Get TrueFolderItem -> pass False.[/quote]

Nice to know the API2 changes are to make things easier to understand. :wink:

23

Thanks for all the fish, um, hints. :slight_smile:

24

I wanted to do test with one of my rpogram but Alias are resolve as I drop them on ListBox (I do Obj.FolderItem ).
Then I don’t know if we have to put True or False if we want the Alias or the Target :confused: .

Edit : I checked with a PathString
TextField1.Value contains a Path of an Alias

f_Elt = New FolderItem(TextField1.Value, FolderItem.PathModes.Native, False)

return the Alias (then f_Elt.IsAlias = True and f_Elt.NativePath = TextField1.Value)

f_Elt = New FolderItem(TextField1.Value, FolderItem.PathModes.Native, True)

return the Target pointed by the Alias, then f_Elt is not an Alias except if no target

25

[quote=458200:@Thomas ROBISSON]Sam, I understand the opposite, you get the alias itself if you pass False, and the file pointed by the alias if you pass true.
Then to replace GetFolderItem -> pass True, Get TrueFolderItem -> pass False.[/quote]
I tried to look at the docs from the link I shared and it seems all the information has gone. I am not running 2019r2 (yet) so I’ll take your word for it.

IMHO it should always return the actual file, and if you want a resolved alias, that should be a further function. However I understand that they don’t want to change this as the default has always been to auto-resolve aliases.