Bart van Andel wrote: > Upon installation, Hugin registers its file type (.pto). I found > references in 3 places: > - hkey_classes_root > - hkey_local_machine\software\classes > - hkey_current_user\software\classes > > The first and the second are system-wide and thus require elevation or > administrative rights to add/modify. The last option does not require > this. Why are the references found in 3 places?
I guess it is to register .pto files with Hugin system-wide and not just for the user performing the installation. > If the settings could be moved to a .ini-file there was a discussion in that sense in the past. I personally prefer the .ini file. I don't recall why the registry location has been retained. With an .ini file it would be truly possible to keep two versions of Hugin on the same box. As it stands now, there is a chance for conflict because both use the same registry location. > and file associations are abandoned I don't think that abandoning file associations is good, but we could make it optional for those who trade off convenience as in double-click on a project file to convenience as in run off a USB stick. Yuv --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hugin-ptx -~----------~----~----~----~------~----~------~--~---
