InstallAware

I missed to mention that you can also use a custom folder selection dialog in place of a "Folder selector" function. I mean a dedicated setup dialog that only has a "Browse for folder" control.

This can be displayed as result of a dialog button selection (eg. a Browse button in a modified Destination dialog and where the "Browse for folder" control has been removed) and then similar to the sample, you can apply all the required parsing operations via script.

Hope this helps you.

Regards

Hello Francesco,

first of all: with a combination of These I implemented a culture neutral Version of the Dialog.

A behaviour you should add to your bug list and your (most urgent) ToDo list:
When copying a line of code in your MSI Editor, pasting and editing it, the line keeps the old value although it displays the just edited (this can be noticed only when pasting MSI Code to the for example Notepad and look for the values (and of cource at runtime, when the setup shows a wrong behaviour )). This makes it very hard to debub setups and find errors, when you read over it and all you read is okay.
Today, I noticed a similar behaviour in your Dialog/GUI editor:
I insert a Label, it's getting for example the name "Label2", in the ObjectExplorer I set the property "Caption" to display the value of one of my variables, say $VALUE1$. Sometime later I set the caption to display $VALUE2$, it still displays the value of my variable$VALUE1$.
I delete this label completely and insert a new one and set the caption to display $VALUE2$: same beviour. Why? The label got the same name "Label2". I do lots of editing. As soon as a label again gets the name "Label2" it will display the value of the first variable I ever entered in the caption to be displayed. Also renaming the label did not help. Inserting another label and afterwardsdeleting the Label2, fixed this.

So, the MSI Code Editor, and also your GUI/Dialog Editor have a big problem receiving new edited properties. This makes developing a setup using InstallAware a very time consuming task.

Dear Anja,

Honestly I don't see the possible bugs your are reporting.

For what concerns the MSI Code Editor, this doesn't keep the old values after pasting and editing code lines. I used Notepad as well to verify it.

I can also assure you that I don't see the problem you seems to have with the dialog editor.
Are you sure to effectively select the pasted object and not the original?

...are you using a VM as development system?

Regards

Years later ...

The topic request is still not solved.
Now, after finally having figured out how to get rid of the previously never changing language in the small glassy window at the beginning of the installation by using the predefined compiler variable LOCALIZATION_PRECEDENCE=USER, I was actually hoping, that this even more annoying issue was solved as well.

My hope was in vain. If you can get the language of the current user into the setup, why does it seem to be an unresolvable problem to get the user's format settings as well?


Yes, I have tried all the samples you provided and it seems possible the get an acceptable result.
But do you think it is acceptable, that every user of your software who needs to distribute to countries with other formatting rules than the ones you use, has to go this path, instead of resolving this issue once and for all at your side?

This has been fixed by the latest IA x15 minor update v.32.22.
- Thousand separators non-localized

Thanks.