Browse Folder Dialog: Button width too short

[clint]

Hi,

In Enhanced mode, is there any way to change the width of the buttons in the Browse for Folder dialog?

In the German language, the Select/Ok button is too short and the words are truncated.

(I already know how to do this when not using the enhanced mode).

Thnak you!

clint

[Eusebiu]

Hello,

In Enhanced mode, is there any way to change the width of the buttons in the Browse for Folder dialog?

I'm afraid that the "Browse Folder" dialog is displayed using the operating system predefined dialogs, so the user cannot change the width of the buttons using Advanced Installer.

In the German language, the Select/Ok button is too short and the words are truncated.

You can take a look on the following thread which discuss a similar problem.

In order to achieve that you can go in the Translations Page page and translate default strings from the dictionary.

If you want the changes to be applied to all the projects that you will create in the feature, you can go at the "C:\Program Files (x86)\Caphyon\Advanced Installer 11.4\dictionaries" path and edit the related strings from the "ui_de.ail" dictionary file.

Please let us know if that helped.

Best regards,
Eusebiu

[clint]

Hello Eusebiu,

1. Nice to be able to translate this way! Good stuff!



Developing on Windows 7 Sp1

3. Problem with saving to the Dictionary: Although I clicked "Save changes in a dictionary from repository" and it turned grey, and I saved the project, when I re-opened the project, the changes didn't persist.
It only worked when I opened AI with Admin. Rights.
The repository is not in a protected folder:
Z:\INSTALLATION\Advanced Installer\Repository

4. Problem with testing translation with "Installation UI" toolbar button:
The project builds, but when AI then tries to start the Setup.exe, it fails (see attachment).

This happens even when AI is started with Admin. priviledges, as this is a protected folder.

(The AI setting for the build cache is in a nin-protected folder: W:\AI_InstallCache)

5. When I build the Setup and run using the normal Product Build (AI started with normal user priviledges), the changed and saved text (translation saved with AI started with Admin priviledges) for the control shows up properly using Enhanced Mode on a XP machine. (Happy)


Please let me know about what I can do about the problems under points 3 and 4.

Thank you.

clint

[Eusebiu]

Hello,

Problem with saving to the Dictionary: Although I clicked "Save changes in a dictionary from repository" and it turned grey, and I saved the project, when I re-opened the project, the changes didn't persist.
It only worked when I opened AI with Admin. Rights.

I've tested your scenario and this seems to be an Advanced Installer issue. A fix will be available in a future version of Advanced Installer, thank you for bringing it to our attention.

Problem with testing translation with "Installation UI" toolbar button:
The project builds, but when AI then tries to start the Setup.exe, it fails

I'm not sure why you encountered the this behavior. Are you sure that the file is not in use when you try to build and test the installation?

In order to have a better view about this, can you please send us a small test project which reproduce this behavior to support at advancedinstaller dot com, so we can investigate it? Also, can you please tell us the version of Advanced Installer and the Operating System you have on your machine?

Best regards,
Eusebiu

[clint]

Hi Eusebiu,


I found out what the problem was. It helps to investigate the error message thoroughly:

I looked in the temp folder where the Setup.exe was being created, and found the following:

Transl_Build.JPG (102.18 KiB) Viewed 10912 times

I works now.

Thank you!

clint

[clint]

Hi Eusebiu,

I do have one more question concerning the translations:

My project is buit using the German build language (no english selected).

When I select "English" and build the package, the all of the Microsoft language Merge Modules cause errors.

There are 11 in all, and are directly from MS.

AI Error:
Could not open module: Z:\INSTALLATION\Advanced Installer\REGIE 68\MergeModules\tabctde.msm. Error:The language of the current build is not supported by the specified merge module.

I suppose I am again just doing something wrong here.

Will I need to create separate builds and packages for this, one with the German language Merge Modules and one without?

Thank you!

clint

[Eusebiu]

Hi Clint,

I'm afraid that a Merge Module cannot be added to a package if it does not contain the same languages as that package.

Will I need to create separate builds and packages for this, one with the German language Merge Modules and one without?

Indeed, you need to create separate packages and include the German Merge Modules in the German package and the English Merge Modules (if you have them) or no Merge Module in the English package.

Best regards,
Eusebiu

[clint]

Alight. Thanky you Eusebiu.

clint

[Eusebiu]

You're always welcome Clint.

Best regards,
Eusebiu