My app's stored files' shape are as unknown files
-
@tomy said in My app's stored files' shape are as unknown files:
My purpose is when someone installs the app
Looks like you misunderstood me and I misunderstood your last reply :-) My point was from the beginning that your app or its installer modifies the registry, not the user.
-
"I don't change the registery but it itself (I think) does that" - sorry, but how and why would registry change itself?!
Ow I din't mean either the rigestery or Windows, I meant the app! :)
(either do it in the installer or in the app),
Yes, this is what I'm looking for. My installer is Qt Installer Framework. And I also have the source code. Which one should I use and how? Is there any step-by-step tut on this case, please?
Please refer to Microsoft documentation: https://msdn.microsoft.com/de-de/library/windows/desktop/ee872121(v=vs.85).aspx
Do you now think I should follow this thread? And don't change the code for that purpose?
-
When you install a software YOU don't change registry but the installer DO change it. The developer who creates this installer take care to make any necessary changes in registry in background. In this case as developer you have to take care for this.
You're right, but how? By modifying the code or using the installer (Qt Installer Framework)?
-
@tomy
If you use installer, this is one time job. After initial settings you can't change them again if for some reason they are changed.
In a lots of apps this is realized as settings "Associate" in the app. Benefits here is that you can change these settings any time. -
Thank you.
So both of you recommend that I usesettings
orQSetting
. I guess it's a Qt class that I can use it in the code so that it applies changes to the registery when the app is being installed on a Windows machine (of a user).
Have I understood correctly? If so, so I should be familiar with such a class and try to figure out where and how in the code I use it. correct? -
@tomy You would use QSettings in your app but not when it is installed. The idea would be to check at start-up whether your file type is registered or not and if not register it.
Yes, QSettings is a Qt class, take a look at its documentation.
But it is worth checking whether Qt Installer Framework supports this use case as it is is actually something the installer should take care. -
You would use QSettings in your app but not when it is installed.
Yes, I know that. If I'm able to change the code so that the app is the way I need, I also can uninstall the previous app and install this new version, or I send it to a friend and they install it on their Windows machine too.
The idea would be to check at start-up whether your file type is registered or not and if not register it.
I don't understand this part.
Yes, QSettings is a Qt class, take a look at its documentation.
But it is worth checking whether Qt Installer Framework supports this use case as it is is actually something the installer should take care.So the first step is to check if Qt Installer Framework supports that or not. And if yes, I use the class QSettings in the code of the app and finally create an new installer and install it.
OK, these are too new for me. I've never done these. How to check Qt Installer Framework for that? If Qt Installer Framework supports that, I then should try to use that QSettings class and probably give it an icon to put on the stored files.
The process sounds by no way easy! :(
Isn't there any straightforward tut on this case?
And have you programmers ever done this? You have done absolutely I think. What is your experience in this case, please? -
-
Good. I edited the package.xml file. And also changed all
@component.addOperation
to@component.addElevatedOperation
in the installscript file. There are three operations all for creating shortcuts.
Now I seemingly should add this line of code into the code:addElevatedOperation("GlobalConfig", "SystemScope", "Company", "App", "key", "value")
I searched for that and found this. It shows no detail on how to use the arguments and where in the code, what
header
or.cpp
file, to use it! :(