<div dir="auto">Thanks for reciting all the places I have to learn about.<div dir="auto">Is it fair to say that each of these other config file duties can be satisfied by the default file that willl be created in the new install?</div><div dir="auto"> I would love to hear your brief summary of the duties of each of these config files!!</div><div dir="auto">THe larger corollary question:</div><div dir="auto"> Is it fair to say that digikamrc as the primary INI is all that is needed to tie the digikam4 database and thumbnails to an unchanged collection?</div><div dir="auto"> </div><div dir="auto">This should preserve:</div><div dir="auto">a tag collection and mapping of tags to images</div><div dir="auto">1 or more album collections (that should have unchanged recursive folders)</div><div dir="auto">indexes to display prepared thumbnails</div><div dir="auto"><br></div><div dir="auto">Thanks Ty</div><div dir="auto"><br></div><div dir="auto"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jan 27, 2022, 4:08 AM Gilles Caulier <<a href="mailto:caulier.gilles@gmail.com" target="_blank" rel="noreferrer">caulier.gilles@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Hi,</div><div><br></div><div>yes there are more config files for digiKam, but the most important is the INI based config file digikamrc:</div><div><br></div><div><div>[F] C:/Users/_account_/AppData//Local/digikamrc</div><div><div><div></div><div><div>[F] C:/Users/_account_/AppData//Local/digikamsystemrc</div></div></div><div><div></div><div><div>[F] C:/Users/_account_/AppData//Local/digikamtagsmanagerrc</div></div></div><div></div><div><div>[F] C:/Users/_account_/AppData//Local/showfotorc</div></div></div></div><div><br></div><div>[D] C:/Users/_account_/AppData//Local/digikam/</div><div><div></div><div>[D] C:/Users/_account_/AppData/Roaming/digikam/<br></div></div><div><div>[D] C:/Users/_account_/AppData/Roaming/showfoto/</div></div><div><br></div><div>Gilles Caulier<br></div><div><br> </div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le mer. 26 janv. 2022 à 16:52, Ty Mayn <<a href="mailto:tyrus.mayn@gmail.com" rel="noreferrer noreferrer" target="_blank">tyrus.mayn@gmail.com</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div> I see that another way of hiding a working program and collection during the transition to a new version is to create a new user and segregate until the new version is proven.</div><div> It seems to me that hiding the digikamrc file alone is sufficient to let the new program show its true colors.</div><div>But let me return to the events of a new install</div><div>1. will the install process seek to use the same "digiKam" folder in Program Files <br></div><div> if so I will ask the install to go somewhere else</div><div>2. digikamrc Is there any other file which is serving as the persistent memory of chosen display and behavior variables for digikam?</div><div> Does the installation code ask for install to probe for digikamrc and inherit/preserve any settings that have been chosen within older version operations?</div><div> Does installation look in /User/user/AppData/Local for at least on occurrence of a digikamrc (evidence of a preexisting install)?</div><div> Are there any other files for persistence of program config,behavior, or carryover data?</div><div> Would it not be sufficient to just hide digikamrc away from /user/AppData/Local during a new install</div><div> and then edit the newly arrived digikamrc for the database path statements?</div><div> I am OK with having a clean slate of default config variables in the newly delivered digikamrc</div><div><br></div><div>3. database files I hope that digikam installation does not go probing through a hard drive looking for possible collections or recognizable names of database files. I much prefer to point a program to its place of work. <br></div><div> So perhaps I dont have to "hide" the database files or temporarily move them off of the drive as I intended in the plan at the top of this thread. So if the install program is not aggressive about automatically searching for existing database in all readable folders then I can temporarily hide the database files simply by not offering a digikamrc file</div><div> <br></div><div> Hiding the entire user is one way to hide the digikamrc file ....is that the only critical file to hide to get a new config? <br><div>Thanks</div><div>Ty<br></div><div><br></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jan 26, 2022 at 12:33 AM Gilles Caulier <<a href="mailto:caulier.gilles@gmail.com" rel="noreferrer noreferrer" target="_blank">caulier.gilles@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Hi,</div><div><br></div><div>To be sure to not break something in config files, I recommend to create a new user account, and to start digiKam 7.5.0 from this account as well without touching all settings from the original account. Like this there is no risk of losing/breaking something.</div><div><br></div><div>Best</div><div><br></div><div>Gilles Caulier<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le mer. 26 janv. 2022 à 06:24, Ty Mayn <<a href="mailto:tyrus.mayn@gmail.com" rel="noreferrer noreferrer" target="_blank">tyrus.mayn@gmail.com</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Now returned to digikam, It's time to upgrade from 6.0 to7.5</div><div>Unfortunately I have to use windows10 for the benefit of a non linux collaborator.<br></div><div>i have looked but not found a howto on upgrade. Can I describe my strategy and receive warning away from any wrong assumptions.</div><div> I plan to install new 7.5 with all evidence of the old 6.0 hidden.</div><div>I will hide the existing config file digikamrc and the 4 database files.</div><div> After the install, I guess I will find a new default digikamrc in the path</div><div>User/AppData/Local (if that default has not changed)</div><div> I expect to be greeted by a welcome wizard that will ask to point to some brand new folders to become albumsbut rather than follow the wizard:</div><div> I hope to return the database files into their original location specified in the older digikam RC<br></div><div> I plan to examine the new config file and pause to compare some of its config variables compared to the older. <br></div><div> Then manually edit the path variables in digikamrc which point to the database files.</div><div> I am not trying to circumvent any tools that might be in the wizard and may be its not oriented to starting up an all new album collection from scratch.</div><div> I am guessing the database files can serve the new version and may change or be repaired with ongoing use (unless warned away)<br></div><div> This seems to be a worthwhile approach for pointing a new program install to an existing collection..... unless this helpful list warns me in other directions.</div><div>Thanks</div><div>Ty</div></div>
</blockquote></div>
</blockquote></div>
</blockquote></div>
</blockquote></div>