Flint for Ignition with symlinked folders causing resource location problems?

Ignition
,
1

I'm am super excited to start using the flint for ignition module and vs extension! I have both installed but I'm running into an problem where I can see the folder structure of my project in the flint project browser but when I select any of the resources it says it is unable to open the requested resource.

In addition I can see the folders for each of my project scripts but they are empty.

I suspect it is because I am using a symlinked data folder, so that I can keep the program files for my various components in a single repo (robot files, vision programs, etc.)

First of all is this likely the problem? If so is there a work around anyone knows or a way to specify a different path where the extension should look for the files?

Or if there is a better way to handle version control that others can suggest I'm willing to change that to make flint work (assuming that the symlinked folder is the problem).

image
image583×604 29.7 KB

image

Notes:

  • The gateway isn't logging any errors when I try and open a resource.
  • I am running the gateway locally.
2

Hi Alex, I haven't ran into this issue before.

You could pinpoint the issue by pointing to the actual directory instead of the symlink if it is all locally hosted. How are you running your ignition instance locally?

You can also raise an issue at:

3

Are you on native Windows, if so you are likely running into a reported Windows issue (# 3). Using WSL would likely avoid it.

4

@Noah_Burnette @kvaneenennaam
Thanks for the responses.

Good idea, I'll post my issue on the github.

You could pinpoint the issue by pointing to the actual directory instead of the symlink if it is all locally hosted.

Short of reinstalling is there a way to change the directory ignition is pointing to?

How are you running your ignition instance locally?

After installing the ignition gateway on my computer I deleted the data folder and add a symlink folder that pointed to the data folder in the repo. Not sure if this answers your question.

Are you on native Windows, if so you are likely running into a reported Windows issue (# 3). Using WSL would likely avoid it.

This is the seems like the issue! Thank you, I'll look more into this.