(2019-03-11, 18:34)Klojum Wrote: (2019-03-11, 16:38)1Underpar Wrote:
Menu customizations & a clean library != Library path changes as per this thread's objective.
Klojum, I am glad you responded to my recent post in this thread. I took a quick look at your profile and see you've been around here a long time, and you have made many posts. I'd imagine you've helped many people and solved many problems. Obviously I want Kodi users, who are looking for a solution to this problem to see this post. I also wanted to make a point to technical people such as yourself. You are exactly who I wanted to see my solution in this years old thread.
Just the fact that this thread is old, and the issue of upgrading storage devices is still a problem, says something in and of itself, but I don't wish to digress. You say "Menu customizations & a clean library != Library path changes as per this thread's objective." I say the objective of this thread is to solve a problem. The problem being that when a Kodi user changes their storage, whether that be a sophisticated NAS setup, or as in my case, a simple external drive plugged into the router, the buttons in the Kodi menu no longer work. The thread offers going into config files, sql, and database files, as a solution. And I imagine if you have the computer skills necessary to find these files and manipulate them, then that solution is here to be found. But what about the
VAST majority of the users of Kodi? The
VAST majority of users don't posses these computer skills. The vast majority of users don't know the letters "DB" stand for database. I guess the vast majority is just out of luck huh?
While you technical wizards are busy impressing each other with your considerable skills, the rest of us just want the upgrade to a new storage device to work. And that's where I came into this thread. I just offer a simple solution to the actual problem. My thought is, if a user has the skill to download and use Kodi, they are likely to have the skill to download a skin that solves the actual problem.
Just because my solution is not myopically focused on the config and database files to change the library path, doesn't mean it's not relevant to this thread and
more importantly, a viable solution to the actual problem, for the vast majority of Kodi users.