Re: [Amsn-devel] Re: [Amsn-commits] msn config.tcl,1.302,1.303

[Jérôme Gagnon-Voyer]

Le 05-11-20 à 17:34, Youness Alaoui a écrit : Humm.. you are right, but I think we should add something as simple as : if {[::config::getKey configurationVersion 0] < $::supported_config_version } { msg_box "Your configuration will be lost due to major changes in amsn's internal functioning." ::config::loadDefaultValues } ::config::setKey $::supported_config_version or something like that... What do you think ? I think it's simpler... we might get a lot of things like that, but it's better... if we change a default value (first, I want logges to be automatically saved!!! and for the new FT protocol, I had to change the key name everywhere... It would be so simple if we have an incremental 'default values' version...) It means that everytime we update aMSN, we lost all the settings? I don't think people will love that. But I don't understand exactly what is supported_config_version variable? BTW I think the problem with logs was that if we put LOGS on by default, then someone who connect without profile, will get all the logs saved and then everybody could read it. It's on by default, currently ::config::setKey keep_logs 1 ;#Save log files: 0|1 p.s.: it reminds me, can someone make sure the default value of keep_logs is set to true ? I think we should force the default behavior of saving the logs...