You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the data I am adding to my cloud drive, there are a lot of images that I would not necessarily need or want to view in the photos tab, such as album artwork from my music library, system icons, etc.
Would it be possible to add a feature that either
allows me to exclude certain directories so the photos tab ignores them when loading images (maybe the .megaignore could be a part of this?)
OR
add an option to specifically set which directories the photos tab should load images from. In this case I only really care about my photos folder, after all.
(archived concept art from some graphics design work I did a few years ago, I really dont need to be reminded of it)
Please let me know if this would be more on the sync side.
The text was updated successfully, but these errors were encountered:
It is already on our roadmap and will be added to our services in future releases.
Have a MEGA-awesome day and contact us should you need any other assistance.
We appreciate all feedback and are working to improve and integrate new features with this feedback in mind.
In the data I am adding to my cloud drive, there are a lot of images that I would not necessarily need or want to view in the photos tab, such as album artwork from my music library, system icons, etc.
Would it be possible to add a feature that either
allows me to exclude certain directories so the photos tab ignores them when loading images (maybe the .megaignore could be a part of this?)
OR
add an option to specifically set which directories the photos tab should load images from. In this case I only really care about my photos folder, after all.
(archived concept art from some graphics design work I did a few years ago, I really dont need to be reminded of it)
Please let me know if this would be more on the sync side.
The text was updated successfully, but these errors were encountered: