About Andreus

Andreus · ‎Feb 04, 2022

So the key point is IMAGExOPT. Any of UPPER_LEFT, UPPER_RIGHT, LOWER_LEFT, LOWER_RIGHT designate dialog corner where offset 0,0 is placed for. Offset is positive from corner choosen to the dialog center. If you choose UPPER_RIGHT the offset shows how upper right corner of image shifted relative to upper right corner of dialog. Answers for my questions above. Can I place more or less than 3 images? - Yes Is image ordering important? - Yes. Image number is actually Z-orger. Last one is topmost. Can I use negative image offset? Yes! Actual for VCENTER and HCENTER, but works generally. Can I place image over filled rectangle? Images is Always placed over("above") all rectangles. Rectangle number is it's Z-order. I hope it helps someone.

Andreus · ‎Feb 04, 2022

InstallShield technical support can't solve simplest case for a week. It looks I help them to learn how their product functions. No reply for several days even for High level case. I have to spend my time for guess and try game due to pure doc. But I finally got the knowlege.

Andreus · ‎Feb 03, 2022

I've got a task to change visual style in our InstallScript based installer. Skin Customisation Kit has one page manual and two samples. According to manual Skin includes filled rectangles, images, buttons. Default dialog has to be of size 460x305 dialog units. Image Positions(described as offset) measured down-right in dialog units from top leftmost dialog corner, I guess. My first idea was just use one bitmap of proper size to replace all dialog background. It doesn't work. Skin of one bitmap silently generates Zero size .isn file. Why? No explanation but both samples use 3 images (top,left,bottom). Description on image placement is 4 lines IMAGES=n (number of images) IMAGEx=file name of image IMAGExPOS=x offset,y offset (in dialog units) IMAGExOPT=TRANSPARENT, SCALE, VCENTER, HCENTER, UPPER_LEFT, UPPER_RIGHT, LOWER_LEFT, LOWER_RIGHT (pick any) So does anyone knows what exactly VCENTER, HCENTER, UPPER_LEFT, UPPER_RIGHT, LOWER_LEFT, LOWER_RIGHT mean and what is IMAGExPOS offset is relative to? Can I place more or less than 3 images? Is image ordering important? Can I use negative image offset? Can I place image over filled rectangle? Please help - support is extremely slow...

Andreus · ‎Dec 28, 2020

I've got InstallScript project developed with IS2012 couple of years ago by other developer. It's multy-instance project designed to install family of our products with one IS project. Each project release is conceptually different product with unique GUID value stored in release overriden path variable ProductGUID . ProductCode (renamed ProductGUID of IS2012) project property can't be associated with path variable by IS IDE - Project Settings has interface to assign static GUID string only but not path variable like Product Version or Product Name. I've upgraded project to IS2019 and lost multiproduct functionality due to project property 'Product GUID ' rename . Fixing it I've found project xml file was edited directly - Property table contains (now upgraded to IS2019 scheme) <row><td>ProductCode</td> <td><ProductGuid></td><td/> </row> * <ProductGuid> is Release overriden path variable and IT WORKS as expected with IS2012 and IS2019. It looks like half-documented feature or feature in "gray zone", but very convinient. IS help has note changing a project’s product code is typically not necessary and should be approached with caution. but that's not our case. We "switch" GUIDs "with caution". Is it UNSUPPORTED FEATURE? Should I split project into 5 separate ones to keep it supported in next IS releases? What about make it supported and documented? Very much like comments of IS support and developers(silver maintenance). Thank you.

Online Status	Offline
Date Last Visited	‎Feb 14, 2022 05:20 AM

Re: Skin Customisation with InstallScript

Re: Skin Customisation with InstallScript

Skin Customisation with InstallScript

ProductCode as Realease parameter - works but supported?

Re: Skin Customisation with InstallScript

Re: Skin Customisation with InstallScript

Skin Customisation with InstallScript

ProductCode as Realease parameter - works but supported?