Relative Paths in Property Inspector

[Sannyasin Brahmanathaswami]

@ Brian: good question. Now that I think of it… maybe both would be good?

Option 1: If the pref is on, then the check box is checked by default in the PI; otherwise it's not. This allows the user to use full path. Option 2: no check box in PI, just a pref because: assumes no use cases there are that would "break" if the path was always relative. But I don't know if that assumption is correct, and option 1 seems to be "no skin off the IDE" to implement.

Possibly in some secure situation a stack wants to only able to access local resources and would fail to find them, by design, if ported as a package elsewhere. Seems very rare use case to me. One faces this same issue every day in our team… with DTPublishing with doc + links to images, and we all just wish Adobe would make relative paths work "out of the box, everywhere, all the time."

@ Mikey 
a) we understand your use cases… in fact I have the exact same set right here; GIT is in effect the net storage case you describe, and albeit instead of a mounted drive you have your cloned project folder on disk… on another project we used Dropbox.
b) Sorry to be tedious, but you did not confirm: if you keep the stack and the image in the same folder on the "cloud" drive that appears as a mount point on your system… 

~/Dropbox/Pet Project/animals.livecode
~/Dropbox/Pet Project/img/dangerous-pets/tiger.jpg

do relative paths work? of course I could test here, but just want to be sure your context is the same.

c) Yes, I will file an QR enhancement request… and agreed they should be considered together, 

But first: if your answer to b) above is "No" that the relative path on a mounted instance of your cloud drive doesn't work then we have a different problem, 

OR 

if the answer is "Yes" it does work… then we do indeed have the same/parallel request and I can just append your QR

BR


Brian wrote:

    So the ask is for a check box in the PI (near the source field with a label
    like “Relative path”)? And when checked, the PI would automatically trim
    the path to be relative to the stack file (probably with the assumption
    that it only goes down the hierarchy).
    
    Or are you asking for a preference that would default to relative path
    names when choosing files in the PI?