2015-01-14, 02:26
I'm switching over to network shares for loading files via SMB, and there seems to be a problem with how Advanced Launcher adds shared files by default. Whenever I add or change items to launchers, anytime I try to launch them I get an error: "File [filename] not found."
This appears to be related to how the program enters filenames into the launchers.xml file. The file paths use the format "smb://[Computer Name]/path..." (without quotes) when added via Advanced Launcher. This goes against the path naming conventions the program uses for local files. However, when I switch to the file path naming convention for SMBs used by Windows, which is "\\[Computer Name]\path..." (again, without quotes), files work fine. Notice the lack of the SMB prefix and the backward slashes.
Is this an error on Advanced Launcher's side? I can change the file paths fine and make them work via the xml file, but I'd prefer that it work fully with just the program.
This appears to be related to how the program enters filenames into the launchers.xml file. The file paths use the format "smb://[Computer Name]/path..." (without quotes) when added via Advanced Launcher. This goes against the path naming conventions the program uses for local files. However, when I switch to the file path naming convention for SMBs used by Windows, which is "\\[Computer Name]\path..." (again, without quotes), files work fine. Notice the lack of the SMB prefix and the backward slashes.
Is this an error on Advanced Launcher's side? I can change the file paths fine and make them work via the xml file, but I'd prefer that it work fully with just the program.