The VideoLAN Forums

and have automatic updates disabled, for all users. This is needed to manage all applications and Application Versions.

and have automatic updates disabled, for all users. This is needed to manage all applications and Application Versions.

but they can use Help>Check For Updates

You need to recompile to deactivate updates

You need to recompile to deactivate updates

Recompile? So if someone wants to use VLC in a business environment they have to recompile the source code to use it in a proper way? Maybe some improvement for next release?
I think it's strange that update is user based. Normally an update mechanism is based on a computer level (registry key or something).

IF I want to recompile, what to do?

We looked into the solution to change the config file and save the config file in the Default user folder. Unfortunately this isn't working.
Our clients run Windows 7 SP1 x64.

Sure... But how many users in a business environment click on Help - Update? Plus, users are not able to update, because they don't have any permissions. The point is, that I don't want to bother the users with a message "there is a new update available..."

Notifications don't require immediate user action and users can freely ignore them.

Developers and designers often want to present their notifications in a way that users can't ignore. This goal completely undermines the primary benefit of notifications because it would break users' flow. If users are distracted by your notifications or feel obligated to read them, your notification design has failed.

Code: Select all

If business wants business-friendly VLC development, they can sponsor those development. I don't see why we should do that on our free time.

Disabling auto-update by setting a config file i a user folder worked with older versions of vlc, so we just want to have the same option with 2.1.0?

I have been doing lots of testing with different versions of VLC trying to come up with some sort of solution for vlcrc file not to be ignored for new users. My observations are as follows:

1) In VLC versions < 2.1.0 and Windows XP SP3 vlcrc is working as expected i.e. vlc.exe fires up for the first time and creates C:\Documents and Settings\%Username%\Application Data\vlc\vlcrc file and upon closing two extra files named vlc-qt-interface.ini and ml.xspf are being added. Now if you move the vlc directory from C:\Documents and Settings\%Username%\Application Data to C:\Documents and Settings\All Users\Application Data next time vlc starts you don’t get “Privacy and Network Access Policy” and auto update popup window and in the background vlc folder will get copied from All Users to profile of your user opening vlc (when you close the application). This behavior means that C:\Documents and Settings\%Username%\Application Data\vlc\vlcrc and vlc-qt-interface.ini are acting as global configuration files for VLC which is what we want.

2) In VLC versions < 2.1.0 and Windows 7 SP1 vlcrc is being ignored when placed in C:\ProgramData\vlc – this simply doesn’t not work like it used to in Windows XP SP3 using the same version – tried on 2.0.6 and couldn’t get to to work in Windows 7 – Windows XP works fine as per point 1 and you’re getting at least sort of global configuration file….

3) In VLC version 2.1.0 vlcrc is ignored no matter if you’re using Windows XP and Windows 7 so the behavior definitely changed with this new and latest release.