Insert image act strange in own created folder structure

[henkjans]

Hello,
I'm facing the next very irritating issue, which seems to occur not constant. I mean: a period of weeks it occurs and then some weeks not and then again.
What happens: I copy an image I want to use in de following sub folder(structure):

\\Flare_project\Content\Resources\Images\My_sub_folder\example.png

When I insert it into a topic, Flare prompt me the following: "Copy to Project" (see attachment, displayed filename and folder structure is irrelevant)

Strange, because I think its already in the Flare-project (see folder structure above).

When I accept, Flare copies the image to the default images folder:

\\Flare project\Content\Resources\Images\

With the result that the same image is 2 times available in the project. And that's unclear to work with and uses to much space.

And then, suddenly, the above described process stops and works like it should. That means that Flare inserts the image from the sub folder into the topic without making the extra copy.

Somebody any idea??

[AlexFox]

This looks like you are mapping images as External Resources, which you don't need to do unless they are collaborative files stored on some network mapped drive or similar. Just drag the image into your actual Flare Resources/Images folder and it should never go anywhere, unless you use source control and you switch to a branch that doesn't have that image yet, of course.

[henkjans]

Hello Alex,

thanks for your reply.

By typing my answer on it, I find the answer, I think.
When I inserted a picture to support my answer to you, I saw the following: (see attachment)

Flare act's different when the full path to a server is used or when a drive letter is used to that server.
In the attachment:

\\GSE-dc01\GSE\Intern vs. I:\Intern

When using a drive letter, Flare works like I wish. Using sub folders and no copies.