Skip to content
⌘ NSIS Forum Archive

UNC specification for filenames

4 posts

BGIdev#

UNC specification for filenames

I am creating an installation package for installing the company software on the workstation at client sites. As the installation package for the software resides on the network, I prompt user to specify the network location to find such file.

I have this working for user type in drive/path (with Auto-complete) in a textbox using the OnChange function, and a browse mode using the SelectFolderDialog function.

When I enter the network specification in the textbox with the drive/path specification, everything functions smoothly. However, when entering a UNC, there is a significant lag in response as I type the backslashes.

Any suggestion on improving the response when entering a UNC?

Thank you,
Anders#
Are you doing the Autocomplete yourself or are you using the Windows autocomplete? I don't think there is much you can do about this either way. A custom plug-in could perhaps do it on a background thread but that could only cure the responsiveness, not the waiting time.
BGIdev#
I am using the call of the SHAutoComplete() function.

Here is the block of code per creating the textbox with the OnChange and AutoComplete functionality:

${NSD_CreateLabel} 20 120 100% 12U "HDIS Location on Network"
${NSD_CreateText} 20 135 300 20U $hdispath
Pop $tb_hdispath

GetFunctionAddress $0 CheckFolder
nsdialogs::OnChange $tb_hdispath $0

; set manual entry of drive/path to auto-complete as user types in the path
System::Call shlwapi::SHAutoComplete(p$tb_hdispath,1)

Thanks,
Anders#
Does it get better if you remove nsdialogs::OnChange? There is not much you can do to make SHAutoComplete faster.