Hello Roland,
I figgured out that the prepareDLG MUST exit with "close current dialog" and "RETURN" and not with "display a specific dialog" . Otherwise there is an errormessage with the FolderDLG. No "path defined" or so. At the first look there is no relation between this dialogs.
I'm afraid I don't fully understand what you mean. Can you please give us more details about this (maybe exemplify)? Also, if there is a bug can you send us a test case?
I like the dialog repository but for me its a bit stiff. Is "move to repository" the same as copy to repository.
Why can't I store my own dialogs no matter what kind of to use them in other projects? They are stored as xml. so it should'nt be a problem. My idea is something like a tex-module repository
like in ms-word or so.
The "Move To Repository" option export a dialog in the
Repository directory, so you have the possibility to use the related dialog in another project.
What else I've noticed ist that the import of a msi-installer, even if it's made with AI doesn't import everything. Some dialogs are missing and some actions referring button object are missing.
Such as the prepareDLG's "Next" button has lost it's action. Nothing defined. And so on...The LicenseAgreementDLG and the ShortcutDLG are not imported at all.
Please note that the import features in Advanced Installer (the Repackager, the Import MSI feature etc.) are intended to be used to get a starting point for your installation package, not to completely reproduce other installation packages. The Repackager tool captures only the effects of the installation (the changes made on the system). If the original installation package executes custom code (programs, scripts etc.) then only the effect will be captured (registry entries, files and folders etc.).
Also, after repackaging an installation some adjustments may be necessary in order to obtain a working installation package.
All the best,
Daniel
FOLLOW US
Get the latest news in Application Packaging