flameshot.ini for all users on Windows

[dirmhirn]

can I place a flameshot.ini in the program files, to enforce some settings for all users?

[Patric-ITV]

I second that!

We are just evaluating Flameshot in a citrix environment, and it would be great if one could set a configuration file for all users.

At least I was able the set the autostart option for all users by creating a registry key with a GPO. But it would be a nice addition if I could disable the "automatic check for updates" option for all users.

Patric

[ElTh0r0]

The ini file location is coming from this code part and currently set to UserScope

flameshot/src/utils/confighandler.cpp

Lines 200 to 205 in 7033f73

	ConfigHandler::ConfigHandler()
	: m_settings(QSettings::IniFormat,
	QSettings::UserScope,
	qApp->organizationName(),
	qApp->applicationName())
	{

You could try to change it to the following (not tested by me!):

 ConfigHandler::ConfigHandler() 
   : m_settings(qApp->applicationDirPath() + "/flameshot.ini",
                QSettings::IniFormat) 
 { 

As "normal" user's should not have permission to touch any files in 'C:/Program Files', I don't know what will happen, if a user changes a configuration through the Flameshot user interface - maybe nothing happens, maybe an error message is shown 🤷‍♂️!

Even if the above works, I can't see a 'clean' solution in the code yet for deploying Flameshot correctly depending on the user's preferred location for the INI file:

• UserScope: 'C:/Users/MrX/AppData/Roaming/flameshot' (on Windows)
• Inside the installation folder
• SystemScope: 'C:/ProgramData/flameshot' (on Windows)

[EnigmaSolved]

If portable mode is eventually fixed/completed (such that the .ini is stored next to the .exe in portable installations) then it seems like that would provide the ability to do what you all are wanting, I think.

[ElTh0r0]

See #4531