All that stuff is really good stuff but anyway that won't be for
0.95, we can keep it for later
It's alreafy fixed for Windows sounds, png.tcl, tclzlib, qtplay and
other things, I'll update this task list later
Le 05-11-20 à 17:45, Youness Alaoui a écrit :
On Sun, 20 Nov 2005 17:39:25 -0500, Jérôme Gagnon-Voyer
<[EMAIL PROTECTED]> wrote:
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.
well, not everytime... only when we think it's better.. maybe once
every 3 or 4 releases...
But I don't understand exactly what is supported_config_version
variable?
it should contain the current version that we support.. for
example, if your config file has a configurationVersion of 3 and
the ::supported_config_version is version 4, then we would drop the
whole settings and use the default values instead..., if it's the
same value, then we use the user's configuration
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.
yeah, that's one problem, I think it should be on by default, but I
also think that we should have a way to check if the user is
connected through a profile or not and add code for it in the
logging system, chat and webcam logs.. remote control, etc... we
should always add the code to make sure the user has the right to
do what he does (save logs for example)...
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...
--
KaKaRoTo
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc. Get Certified Today
Register for a JBoss Training Course. Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_idv28&alloc_id845&op=click
_______________________________________________
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc. Get Certified Today
Register for a JBoss Training Course. Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_idv28&alloc_id845&op=click
_______________________________________________
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel
