With Textpad 9.5.2 and the previous version there is a problem when typing the network name into the folder field at the top of the open dialog. If the type in just the machine name, e.g. \\fred, it does nothing but assuming fred has drives shared adding another \ will show the list of shares but still they won't open. If the drive is mapped then all seems to work OK.
This was not a problem with Text 7 where you could type in the machine name and press return the open dialog would populate the main part of the screen with the shared names.
At one point I thought this was peculiar to linux shares but subsequent checking shows that it is a problem with all shares.
One other point, this verision does not show QuickLinks where version 7 did.
Open file dialog problems using network names
Moderators: AmigoJack, bbadmin, helios, Bob Hansen, MudGuard
Re: Open file dialog problems using network names
A couple of other thing I have just noticed.
When you try to get to a file on a remote system the display is very slow to respond and can actually hang up completely. In fact I have just had to kill TextPad because it completely hung.
When I provide the name of a linux samba share I get the busy switch to box up and when I switch to it brings up the start menu.
The other thing is if I open a file from a local drive and then use the open dialog the location is shown correctly. If I have a file open from a share the open dialog shows the files but the location at the top says Desktop.
This is all Windows 10.
When you try to get to a file on a remote system the display is very slow to respond and can actually hang up completely. In fact I have just had to kill TextPad because it completely hung.
When I provide the name of a linux samba share I get the busy switch to box up and when I switch to it brings up the start menu.
The other thing is if I open a file from a local drive and then use the open dialog the location is shown correctly. If I have a file open from a share the open dialog shows the files but the location at the top says Desktop.
This is all Windows 10.
Re: Open file dialog problems using network names
Please try using the standard file open dialog box:
Configure » Preferences » File » Use the standard file open dialog box
Configure » Preferences » File » Use the standard file open dialog box
Re: Open file dialog problems using network names
OK, now I have another problem, which probably relates to this although it is not specifically opening files.
I have two files open from the same share. Both are visible in the main window and I can select either. If I try to compare them TextPad says that one is not cannot be opened. Then I thought to make a minor change to that file and clicked on file save and up comes the saveas dialog. Both files were originally opened by double clicking from explorer and the other file will save directly after a minor change.
I have two files open from the same share. Both are visible in the main window and I can select either. If I try to compare them TextPad says that one is not cannot be opened. Then I thought to make a minor change to that file and clicked on file save and up comes the saveas dialog. Both files were originally opened by double clicking from explorer and the other file will save directly after a minor change.
Re: Open file dialog problems using network names
Sorry, only just saw the response and the standard dialog does seem to fix the issues. I didn't even realise there was such an option and I'm not entirely clear what the new version achieves and why it is the default.
Re: Open file dialog problems using network names
It seems that something else happened with respect to the compare. The file had disappeared and, to the bext of my knowledge, I didn't remove it. Unfortunately I have no way of knowing what removed it so I can't directly blame TextPad.
Re: Open file dialog problems using network names
The new file dialog matches the selected appearance of TextPad. Unfortunately, it cannot take advantage of the cacheing that the standard one uses, so its performance is not so good with network file systems.