For this post....
FILES = "Files" category found in "Main Menu"
PATH = User determined custom path location that FILES opens into
OVERVIEW
I apologize because this is kind of difficult to explain because there is a main topic that consists of a couple issues.
Issues
1) Navigating back to highest level of your content folder in FILES
2) BACK button goes beyond the custom user set path for FILES
Main Post Topic/Solution
-I believe these issues can be solved by allowing the set path for FILES, to be viewed as being the highest folder level.
Which could be a setting that contains three different parameters regarding how the BACK button functions in FILES.
PATH EXAMPLE
Users can set a custom path that FILES opens into.
For this example I am going to pick a non typical approach to setting up a path just to emphasize my point
LEVEL-1/LEVEL-2/LEVEL-3/Content/Genre/Artist/Album
LEVEL-1 = the highest folder level found on device
Content = this is the folder/level user sets as PATH
Album = the lowest folder, that contains files
ISSUE 1
If user is in the Album folder and wants to get back to the Content folder they have to hit the BACK button over and over until they get to the Content folder, there is no way to just return to that folder (like how "Menu" button bring user back to "Main Menu").
Which is not necessarily a real issue on its own, as long as folder depth is not many levels deep, but not an issue to have to hit BACK button a couple of times. Just pointing out this observation and this also helps explain issue 2 and solution setting I will mention later as well.
ISSUE 2
FILES opens up into custom PATH.
To me I view this PATH (which in example path is the Content folder) as being the highest folder level that I would want to be visible in the FILES category and would expect that hitting the BACK button when in this folder to take me to the MAIN MENU.
However this is not currently the case in RB.
If in Content folder and you hit the BACK button, it does not bring you to MAIN MENU, it brings you to LEVEL-3
You then would have to hit BACK three more times to get to MAIN MENU.
If instead you hit BACK two times to get to the highest folder level which is LEVEL-1
you would then see the following folders
LEVEL-2
Playlist
To me, all of the LEVEL folders would not need to be viewed/accessed.
Also Playlist folder is not needed either because this category can already be accessed through the MAIN MENU if desired.
SOLUTION
The solution I have for this would be to add another setting for the custom PATH that the FILES enters into.
This setting would basically be how the BACK button functions when in this custom PATH within FILES and would contain 3 parameters that would do the following....
-navigate to level above (which is the current default)
-make user custom folder the highest level, where BACK button would bring user to the MAIN MENU
-make user custom folder the highest level, where BACK button would do nothing, would stop here (no higher level, no MAIN MENU) user would have to hit MENU button if they wanted to return to MAIN MENU.
The first parameter would allow the current default behavior and the other two parameters would solve all issues mentioned above.
Thank you to anyone who reads this
Hopefully this makes sense and is something that would be considered to be added to RB