Problem with custom icon

[m.iannozzi]

Hi,
I have customized icon in components/com_jdownloads/assets/images/* and copied all new icon in /images/jdownloads/
All works good for images in /images/jdownloads/ subfolder but for every update Jdownloads replace file in components/com_jdownloads/assets/images/* and it doesn't use files in /images/jdownloads/ folder root.
Jdownloads consider only subfolder in /images/jdownloads/
For all other images it still to use for example /components/com_jdownloads/assets/images/upload.png also if I have /images/jdownloads/upload.png

[ColinM]

I am not quite sure what you are asking so I have put what I believe you mean - please excuse if I have misunderstood.

I believe what you have noticed is that for the most part jDownloads is using images from subfolders in /images/jdownloads/

But there are some, such as the upload image upper.png, that are taken from directory components/com_jdownloads/assets/images/
However directory components/com_jdownloads/assets/images/ is replaced on each update of jDownloads

What you are suggesting is that images which appear in the front end are:
either taken from the relevant subdirectory in /images/jdownloads/
or that images in directory components/com_jdownloads/assets/images/ are only inserted if they are not already present.

This would then allow use of a replacement image.

Is my interpretation correct?

[m.iannozzi]

Hi Colin,

I am not quite sure what you are asking so I have put what I believe you mean - please excuse if I have misunderstood.

It's guilt of my  bad english.

I believe what you have noticed is that for the most part jDownloads is using images from subfolders in /images/jdownloads/

Yes, I see

But there are some, such as the upload image upper.png, that are taken from directory components/com_jdownloads/assets/images/
However directory components/com_jdownloads/assets/images/ is replaced on each update of jDownloads

Yes, I see. I have customized also this image so they are raplaced on each update.

What you are suggesting is that images which appear in the front end are:

either taken from the relevant subdirectory in /images/jdownloads/

this can solve the problem

or that images in directory components/com_jdownloads/assets/images/ are only inserted if they are not already present.

and this can solve the problem in the best way because if a custom image doesn't exist in /images/jdownloads tree jdownloads can use image in /components/com_jdownloads/assets/images/ but maybe that with many users this check can cause excessive use of resources. I don't know...

This would then allow use of a replacement image.

Is my interpretation correct?

[ColinM]

I think this would add to the flexibility. So I  will move this to the suggestions list. Presentlyy we are trying to get to a stable release, then look at suggestions