call explorer

BarryStevens

How can I open a folder in windows explorer for the user to see.

BarryStevens

i worked this out:
SRP_Run_Command("explorer ":MainPath,"DOS")

but the dos window flashes up.
Is there a neater way. (or another parameter/option)

KevinFournier

You want to use ShellExplorer (which is a direct WinAPI call). I think it's already defined in OI. Here's some code the opens the users folder:

Compile Function Test(VOID) Declare function Get_Property Declare subroutine ShellExecute hWnd = Get_Property(@Window, "HANDLE") Operation = "explore":\00\ File = "C:\Users\":\00\ Parameters = \00\ Directory = \00\ ShowCmd = 1 ShellExecute(hWnd, Operation, File, Parameters, Directory, ShowCmd) Return 1

DonBakke

I assume you don't need to use this as a file/folder picker? If not, go with Kevin's solution.

BarryStevens

Yep, that was exactly as needed.
Thank you

KDIV

"I assume you don't need to use this as a file/folder picker? If not, go with Kevin's solution. " - is there a function that will act as a file/folder picker? RTI_OS_Directory does not display the files in a folder, GETFILES will return what user has selected as a directory but I will have to display in a popup, its not a folder/file picker.

DonBakke

I was only thinking of the CHOOSEFILE service and the CHOOSEDIR service.

KDIV

Yes, tried and true, but was reviewing the option above as an alternative, see which option provides the most for a user. I need a custom IMPORT/EXPORT function for a client, a lot of the factors will be unknown, so flushing out the best option I can give them, it seems like I keep returning to UTILITY, just want to try something fresh. Client not allowing a lot of standardization with the IMPORT, I understand their perspective. I will probably go with UTILITY for Phase I and try a lot more of the customization for Phase II. Thanks Don.