kfj schrieb am Mittwoch, 9. Juni 2021 um 09:04:59 UTC+2:
> > My intention is to have this bahaviour: if the .pto extension is already > assigned (like, to hugin), and lux is installed afterwards, the first > doubleclick on a .pto after the installation of lux should result in a > dialog which offers the user to keep this association or change it to > another candidate. After the choice is made, the next time someone > doubleclicks on a .pto, it's opened with the application the user has > selected. I think this is perfectly reasonable. Other Windows users, > please comment. > Hugin registers 2 verbs for pto files: open and stitch. I don't how this interacts with the OpenWithProgID. But this may be a reasonable approach. > > Thomas, you're good with windows. Why don't you help lux along? It would > be easy for you the help make the installer do precisely the right > thing, you know about stuff like the registry, which is alien to me as a > linux person. I've published the .iss script on bitbucket, and if you > find fault with it, why don't you change it? You can send in a patch, > and I'll consider it - and so can everyone else. The file is in the > scripts section: > > https://bitbucket.org/kfj/pv/src/master/scripts/lux_setup.iss Sorry, but I don't have experience with this scripts. So I can't help here. I tested Lux again, but it does not match in my workflow. When opening a pto file it is slower and takes more memory than Hugins preview. So I'm faster with Hugin. Also I don't like the self written interface - but that's a matter of taste. -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/6c4d6713-bf2f-41f6-9b0b-9536bdd89512n%40googlegroups.com.
