qt-installer

Disable native Next button in Qt installer framework

人盡茶涼 提交于 2019-12-10 14:16:50
问题 I have to disable standard next button, on my custom page via installscript.qs file. I can disable my own button (that I created in .ui file) via .qs script like this: widget.myButton.setEnabled(false); This man shows that native buttons represented as enumeration and I cannot disable them same way. Controller Scripting manual page shows some interactions with native buttons. Like gui.clickButton(buttons.NextButton) . I go through whole gui object man and don't found anything useful. Qt

How to write the scripts for Qt Installer

梦想与她 提交于 2019-12-08 19:07:00
问题 I'm trying to write my first Qt installer and having trouble. In my installer, in one of the packages, I need to run an .exe file at the end of the installation and add an environment variable as well. I think the way to do it is with the script option in the package.xml file but I don't know how to write that script, I cannot find a step by step explanation of how to do it anywhere. Can someone help? 回答1: I have been recently suffering the same fate as yourself but have managed, for the most

Qt installer framework hide or disable buttons

旧巷老猫 提交于 2019-12-08 04:26:47
问题 I want to hide or freeze the back button on a page ( to be more specific, License Agreement Page). I tried editing control.qs with few methods but it doesn't seem to work. Following is one of them Controller.prototype.LicenseAgreementPageCallback = function() { var widget = gui.currentPageWidget(); if (widget != null) { widget.BackButton.setVisible(false) ; } } 回答1: I'm facing a similar problem trying to keep hide the Next button in the Target Directory page under certain conditions. But your

Installing VC++ Redistributables in a Qt Installer Framework (QtIFW) installer?

不打扰是莪最后的温柔 提交于 2019-12-07 08:10:39
问题 I am building installers for my app with the Qt Installer Framework (v2.0.1). I'm building my app for both x86 and x64 on Windows, so I'm building an installer for each architecture, with different VC++ Redistributables packaged in each (vcredist_x86.exe and vcredist_x64.exe from MSVC++2013). The QtIFW documentation is frustratingly short on details, but I found that I can add an operation in installscript.qs to run the vcredist installer silently after my files are extracted: component

Qt Installer Framework: Translate component description

扶醉桌前 提交于 2019-12-06 07:38:13
问题 I've got Qt Installer Framework QtIFW2.0.1 installed and I had a look at the shipped examples. When I had a closer look at the example translations I learned how I can translate the content of a custom ui file. But what I neither saw in the example nor in the documentation is how I can translate text that is located in the component package.xml file. In the above mentioned example this looks like this: <?xml version="1.0" encoding="UTF-8"?> <Package> <DisplayName>The root component<

Installing VC++ Redistributables in a Qt Installer Framework (QtIFW) installer?

时间秒杀一切 提交于 2019-12-05 10:26:41
I am building installers for my app with the Qt Installer Framework (v2.0.1). I'm building my app for both x86 and x64 on Windows, so I'm building an installer for each architecture, with different VC++ Redistributables packaged in each (vcredist_x86.exe and vcredist_x64.exe from MSVC++2013). The QtIFW documentation is frustratingly short on details, but I found that I can add an operation in installscript.qs to run the vcredist installer silently after my files are extracted: component.addOperation("Execute", "@TargetDir@/vcredist_x64.exe", "/quiet", "/norestart"); But then I have the problem

Qt Installer Framework: Translate component description

穿精又带淫゛_ 提交于 2019-12-04 14:47:05
I've got Qt Installer Framework QtIFW2.0.1 installed and I had a look at the shipped examples. When I had a closer look at the example translations I learned how I can translate the content of a custom ui file. But what I neither saw in the example nor in the documentation is how I can translate text that is located in the component package.xml file. In the above mentioned example this looks like this: <?xml version="1.0" encoding="UTF-8"?> <Package> <DisplayName>The root component</DisplayName> <Description>This component contains a license and translations to German.</Description> <Version>0

Qt Installer Framework: Auto Update

我与影子孤独终老i 提交于 2019-12-02 17:43:05
I'm currently using the Qt Installer Framework and managed to set up an online repository. What I want to know is: Does the Framework provide some kind of "auto-update" mechanism, e.g. a plugin/service that checks for updates every time the program/system starts? Check for updates would be enough, since the installation itself can be done using the maintanance tool. All I could find about this topic was this small sentence: End users can use the maintenance tool to install additional components from the server after the initial installation, as well as to receive automatic updates to content

Workaround for Qt Installer Framework not overwriting existing installation

旧巷老猫 提交于 2019-11-30 22:58:26
This question is about version 2.0 of the Qt Installer Framework. At this point, it is common knowledge for people using the Qt Installer Framework that, without customization, you simply can't overwrite an existing installation through your installer. This was apparently done to resolve some issues that occurred when this was done with the Qt framework. However, for smaller, relatively simple projects, overwriting is perfectly fine and much more convenient than having to manually run the maintenance tool beforehand. I am looking for a solution involving a custom UI + component script that

Workaround for Qt Installer Framework not overwriting existing installation

眉间皱痕 提交于 2019-11-30 17:54:54
问题 This question is about version 2.0 of the Qt Installer Framework. At this point, it is common knowledge for people using the Qt Installer Framework that, without customization, you simply can't overwrite an existing installation through your installer. This was apparently done to resolve some issues that occurred when this was done with the Qt framework. However, for smaller, relatively simple projects, overwriting is perfectly fine and much more convenient than having to manually run the