I wasn't sure which forum to post this in - sorry in advance if I guessed wrong.
I have a file manager and a separate editor that sit nicely under PA - but I need to be able to have the file manager launch the editor.
The problem that I have is that when I launch the editor directly from the PA menu all is well, but if I close it and then launch it from the file manager the launcher throws a warning "The path to (app name) has changed, since it was last started, from 
to (b). ....."
The difference between the two paths and (b) is that one is an "8.3" file-name/directory-name format path (with "~"s in it) and the other is an LFN format path.
Is there a way to suppress this warning in the launcher ??
I trawled through the documentation but couldn't find anything.
TIA
Bob
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
What editor is giving you the problem? And why on earth would any file manager be using 8.3 paths in this day and age?
Sometimes, the impossible can become possible, if you're awesome!
It's not the Editor giving the trouble - it's the launcher I created with the "Launcher" app.
As for why the file manager uses the 8.3 format --- I've asked the question on their forum.
Rgds,
Dave
You're missing DirectoryMoveOK=yes from the [Launch] section of your AppNamePortable.ini file. That lets the launcher know that the app can properly handle a directory change. If it can also handle UNC paths, add in SupportsUNC=yes as well. These are off/warn by default to ensure that a developer/publisher has tested it before packaging.
Sometimes, the impossible can become possible, if you're awesome!
Excellent
That fixed that problem 
I am also specifying :
SingleAppInstance=false
SinglePortableAppInstance=false
in the launch section but it still complains if a local copy is running.
Have I got this wrong in some way ??
I want to be able to launch multiple instances, both from PA and the local disk installation.
TIA
Bob
Rgds,
Dave
SingleAppInstance=false in the Launch section should do that. What is complaining, is it the app itself?
Sometimes, the impossible can become possible, if you're awesome!
No, its the launcher --- the app doesn't care.
I've tried it on a couple of apps - behaves the same
Using PA 10.1.2
and MakeNSIS v2.46.5-Unicode - Copyright 1995-2009 Contributors
The launcher generator seems to be v2.2 - tho' hard to tell.
Bob
Rgds,
Dave