A decade ago, when you were kindly using NSIS to generate proper Windows installers for each release of Leo, I worked on an enhanced NSIS installer. In those days, it was possible to install Python itself for all users of a machine or for the current user only, and I figured out how to handle those cases. My thought was, I would make it possible to install and test a development copy of Leo on a secondary Windows login, using an installation of Python and one of Leo for the current user only. Testing thoroughly on a single machine struck me as worthwhile.
The NSIS installer required careful management of source code to make it work, and the syntax of NSIS scripts was unique. You ended up abandoning it. Regarding extending the *register-leo.leox* and *unregister-leo.leox *scripts: in the pre-Windows-Vista days when I worked on the enhanced NSIS installer, there was no concern with User Account Control privileges, and I chose not to address 64-bit Windows XP. Now, UACs are with us, and Microsoft supports the use of 32-bit applications on 64-bit Windows, so the number of possible scenarios is greater than it was when I worked on this. We also have virtual machine technology that makes it possible to run a testbed without multiple accounts, which might limit the need for the approaches I worked on. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
