automatic installer and new gui test for windows users

General Project and community related discussion.

Moderator: coordinators

Re: automatic installer and new gui test for windows users

Postby dougal2 » Tue Jun 10, 2008 6:53 pm

+1 working here on Vista 64
User avatar
dougal2
Developer
 
Posts: 3075
Joined: Mon Jan 14, 2008 7:21 am

Re: automatic installer and new gui test for windows users

Postby Lotuspec » Tue Jun 10, 2008 6:54 pm

Installation works on Vista 32bit with UAC on but the start menu shortcuts are only added for the admin account (dont know about the desktop icon as I always disable those).
If your looking for the guilty, you need only look into a mirror - V
Lotuspec
Developer
 
Posts: 101
Joined: Mon Nov 19, 2007 1:53 pm
Location: Belgium

Re: automatic installer and new gui test for windows users

Postby Radiance » Tue Jun 10, 2008 11:22 pm

Hi all,

thanks for helping me test this, it seems to work well :)

i'm still figuring out how to add the detection of the blender installation directory,
or allow some alternative input during installation.

anyone (dougal2?) have any experience doing this in NSIS ?

Radiance
User avatar
Radiance
 
Posts: 3968
Joined: Wed Sep 19, 2007 2:13 am

Re: automatic installer and new gui test for windows users

Postby zsouthboy » Tue Jun 10, 2008 11:59 pm

Home now.

Just tried it on XP 64-bit - works fine there as well.
zsouthboy
 
Posts: 327
Joined: Sun Oct 14, 2007 9:28 pm

Re: automatic installer and new gui test for windows users

Postby dougal2 » Wed Jun 11, 2008 12:04 am

Radiance wrote:i'm still figuring out how to add the detection of the blender installation directory,
or allow some alternative input during installation.

anyone (dougal2?) have any experience doing this in NSIS ?


Hang on, let me look at what I wrote....

I use this to ask the user for Lux's directory:
Code: Select all
Page directory "" "" verifyLux
DirText "Please choose the directory where you have installed Lux Renderer:" "Lux Renderer Location" "" "Location of Lux Renderer:"

and the callback verifyLux to make sure the exe's exist:
Code: Select all
Function verifyLux
IfFileExists $INSTDIR\luxrender.exe I1Good
  MessageBox MB_OK|MB_ICONEXCLAMATION "Lux executable not found. I will still install, but some exporter options may not work."
  ; Abort
I1Good:
IfFileExists $INSTDIR\luxconsole.exe I2Good
  MessageBox MB_OK|MB_ICONEXCLAMATION "Lux console executable not found. I will still install, but some exporter options may not work."
  ; Abort
I2Good:
FunctionEnd

...although I no longer fail if it's not found.

I'm not sure about having more than one "Page directory" or how NSIS manages to assign the path from that one page into $INSTDIR - or if you can get a direcory Page to assign to a different var.

Personally, I think NSIS language is quite horrendous, I hope to not have to use it again :x
User avatar
dougal2
Developer
 
Posts: 3075
Joined: Mon Jan 14, 2008 7:21 am

Previous

Return to General Discussion

Who is online

Users browsing this forum: No registered users and 1 guest