> I guess it is to register .pto files with Hugin system-wide and not just > for the user performing the installation.
That does explain using either hkcr or hklm, but not both, as far as I'm aware only one of those is needed for system-wide registration. For per-user registration, registration is also done in just one place (hkcu). > 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. I like .ini approach better as well. If relative paths are allowed, this would enable true portable usage of Hugin (that is, without leaving registry traces). Could someone explain why the registry approach is chosen instead? > 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. Exactly what I meant to say. -- Bart --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
