Re: Relative Paths in Property Inspector

PR submitted: https://github.com/livecode/livecode-ide/pull/1817 For bug: http://quality.livecode.com/show_bug.cgi?id=17287 Not sure how it will be received, but it uses the pref to always use absolute path names for images to decide whether to convert a path to relative. On Sun, Oct 29, 2017

Re: Relative Paths in Property Inspector

This is called a Watch Folder approach and any cloud based system that uses it (nextcloud does sort of, icloud does as well) will work the same way. Pretty slick. Bob S > On Oct 31, 2017, at 11:43 , J. Landman Gay via use-livecode > wrote: > > On 10/31/17

Re: Relative Paths in Property Inspector

On 10/31/17 11:57 AM, Mike Kerner via use-livecode wrote: no I'm referring to the usernames on the machine. I'm using google drive (backup and sync and file stream). I use dropbox for app data storage and transfer. Here is my setup: I created a folder in Dropbox named "Application Support".

Re: Relative Paths in Property Inspector

no I'm referring to the usernames on the machine. I'm using google drive (backup and sync and file stream). I use dropbox for app data storage and transfer. On Tue, Oct 31, 2017 at 11:17 AM, Mark Wieder via use-livecode < use-livecode@lists.runrev.com> wrote: > On 10/30/2017 07:55 PM, Mike

Re: Relative Paths in Property Inspector

On 10/30/2017 07:55 PM, Mike Kerner via use-livecode wrote: So what do you have for your paths? Are your usernames the same? For me, I run into the issue because my usernames aren't the same on every box, so the absolute path varies. Are you referring to the *dropbox* usernames being

Re: Relative Paths in Property Inspector

Hmm. I wonder why I've run into trouble with this. Now I don't remember. On Mon, Oct 30, 2017 at 11:19 PM, J. Landman Gay via use-livecode < use-livecode@lists.runrev.com> wrote: > I have different user names on each machine too. Just set the appropriate > path in the LC prefs on each machine.

Re: Relative Paths in Property Inspector

I have different user names on each machine too. Just set the appropriate path in the LC prefs on each machine. You only have to do it once, and going forward it just works for any other LC versions you install since all versions on a machine share the same prefs file. On 10/30/17 9:55 PM,

Re: Relative Paths in Property Inspector

So what do you have for your paths? Are your usernames the same? For me, I run into the issue because my usernames aren't the same on every box, so the absolute path varies. On Mon, Oct 30, 2017 at 6:49 PM, Mark Wieder via use-livecode < use-livecode@lists.runrev.com> wrote: > On 10/30/2017

Re: Relative Paths in Property Inspector

On 10/30/2017 01:51 PM, J. Landman Gay via use-livecode wrote: I've got my extensionos folder in Dropbox. All my machines have Dropbox installed and it syncs to all of them. On 10/30/17 3:20 PM, Mike Kerner via use-livecode wrote: All I'm trying to "Get" is a simpler way to store the

Re: Relative Paths in Property Inspector

I've got my extensionos folder in Dropbox. All my machines have Dropbox installed and it syncs to all of them. On 10/30/17 3:20 PM, Mike Kerner via use-livecode wrote: All I'm trying to "Get" is a simpler way to store the extensions folder on a network/sync so I get the exact same environment

Re: Relative Paths in Property Inspector

All I'm trying to "Get" is a simpler way to store the extensions folder on a network/sync so I get the exact same environment on every box. On Mon, Oct 30, 2017 at 4:11 PM, Mark Wieder via use-livecode < use-livecode@lists.runrev.com> wrote: > On 10/30/2017 12:45 PM, Mike Kerner via use-livecode

Re: Relative Paths in Property Inspector

Oh right my point was that I am not sure the tilde would work in a Windows standalone, but maybe the engine interprets it either way. And yes, the tilde means user home folder sorry for the misinformation. Bob S > On Oct 30, 2017, at 11:58 , Mike Kerner via use-livecode >

Re: Relative Paths in Property Inspector

Oh right you are. Bob S ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Relative Paths in Property Inspector

On 10/30/2017 12:45 PM, Mike Kerner via use-livecode wrote: One of the cases where it would be nice is the location of the plugins folder ("User Extensions"), which is why I mentioned ~ to begin with. A better way to get that would be revEnvironmentUserExtensionsPath() -- Mark Wieder

Re: Relative Paths in Property Inspector

http://forums.livecode.com/viewtopic.php?f=6=30074 Richmond. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences:

Re: Relative Paths in Property Inspector

One of the cases where it would be nice is the location of the plugins folder ("User Extensions"), which is why I mentioned ~ to begin with. On Mon, Oct 30, 2017 at 3:22 PM, Brian Milby via use-livecode < use-livecode@lists.runrev.com> wrote: > Just clarifying that the two are not

Re: Relative Paths in Property Inspector

Just clarifying that the two are not interchangeable. From the OP, I don’t think ~/ links would be used at all. I am not saying that we should include the ./ but that when discussing relative links for assets that the fixed point should be the stack location and not something anchored to the

Re: Relative Paths in Property Inspector

Yes, Brian. So I'm not sure what you're getting at. On Mon, Oct 30, 2017 at 3:07 PM, Brian Milby via use-livecode < use-livecode@lists.runrev.com> wrote: > ./ is current directory. ~/ is the user home directory. > On Mon, Oct 30, 2017 at 2:00 PM Mike Kerner via use-livecode < >

Re: Relative Paths in Property Inspector

./ is current directory. ~/ is the user home directory. On Mon, Oct 30, 2017 at 2:00 PM Mike Kerner via use-livecode < use-livecode@lists.runrev.com> wrote: > Actually the ~ is a unix convention, so it is also used in Linux. > > On Mon, Oct 30, 2017 at 2:24 PM, Bob Sneidar via use-livecode < >

Re: Relative Paths in Property Inspector

Actually the ~ is a unix convention, so it is also used in Linux. On Mon, Oct 30, 2017 at 2:24 PM, Bob Sneidar via use-livecode < use-livecode@lists.runrev.com> wrote: > The tilde is a MacOS convention. The period should be universal. ./ as > opposed to ~/ > > Bob S > > > > On Oct 30, 2017, at

Re: Relative Paths in Property Inspector

The tilde is a MacOS convention. The period should be universal. ./ as opposed to ~/ Bob S > On Oct 30, 2017, at 10:48 , Mike Kerner via use-livecode > wrote: > > If you use Backup and Sync (the old "Drive"), your folder is ~/Google Drive/ > If you use Drive

Re: Relative Paths in Property Inspector

If you use Backup and Sync (the old "Drive"), your folder is ~/Google Drive/ If you use Drive Stream and do not map the mount point to an alias in the documents folder, the mount point will be a volume. Git was not amused when I switched on the one machine. On Mon, Oct 30, 2017 at 1:39 PM,

Re: Relative Paths in Property Inspector

@Mike I tried to duplicate your 3rd case. Are you on Mac OS X? if I create a stack, place and img in an adjacent image folder and move to the server ("Chola") in the next room… set the img filename to img/tiger.jpg it works @brian ./img/tiger.jpg also works… but really doesn't get us

Re: Relative Paths in Property Inspector

On "b", I have three machines that I use. Two of them use Google's Backup and Sync service, and the other uses Google's Drive File Stream. So in for two of the machines, the answer is "mostly yes" - the difference is the username, as the "Drive" folder is in the user folder. For the the third,

Re: Relative Paths in Property Inspector

@ 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

Re: Relative Paths in Property Inspector

I think you can. Preface the path with ./ which will refer to the path of the executable. And if I am not mistaken, ../ will refer to the parent folder of the application folder. Bob S > On Oct 29, 2017, at 12:02 , Sannyasin Brahmanathaswami via use-livecode >

Re: Relative Paths in Property Inspector

Sure, but if you were to do that, then I should have an LC-wide preference that I can set so that I don't have to fix it for every project. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and

Re: Relative Paths in Property Inspector

What I meant was not that you shouldn't file a QR, but that I think that all the requests for relative paths should be combined because I think relative paths across LC would be beneficial. Sorry for not being clear about that. I have four obvious cases, where I see a benefit: 1) Using multiple

Re: Relative Paths in Property Inspector

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

Re: Relative Paths in Property Inspector

BR: are you keeping your stacks next to the images? like this ~/Dropbox/Pet Project/animals.livecode ~/Dropbox/Pet Project/img/dangerous-pets/tiger.jpg and if you set the image filename to "img/dangerous-pets/tiger.jpg" it fails? -- Mike Kerner wrote: it is related. As soon

Re: Relative Paths in Property Inspector

it is related. As soon as I saw your post I said "gee, that looks familiar". On Sun, Oct 29, 2017 at 3:02 PM, Sannyasin Brahmanathaswami via use-livecode wrote: > Backstory: > > Sometime back in a round with HQ we got the engine to "remember" relative > path

Relative Paths in Property Inspector

Backstory: Sometime back in a round with HQ we got the engine to "remember" relative path settings for the filenames of images/players etc.. such that it would not default to full path from root on the drive which makes the path unique to that user and no longer portable… so "relativity" go