Subj : JS Object save_msg()
To   : Digital Man
From : deon
Date : Wed Dec 18 2024 12:27 am

 Re: JS Object save_msg()
 By: Digital Man to deon on Mon Dec 16 2024 10:09 pm

Howdy,

>  > date = strftime("%a, %d %b %Y %I:%M:%S %z",time());
>  > // Tue, 17 Dec 2024 02:32:19 +1100
>
> MsgBase.save_msg() will using the current date/time and time zone when
> saving a message. You have a reason to not do this?

Yes - I'm setting the time of some messages to the same time of a file (obtained by new File().date - which also is returning a time_t)

> You shouldn't use the 'date' property unless you have to. Either use the
> default (current date/time and zone) are set the when_written_time and
> when_written_zone header fields instead.

OK, I'll try. What is a valid use case of using the "date" property - I'm curious since it is a valid argument?

>  > date = strftime("%a, %d %b %Y %I:%M:%S %z",time());
>  > // Tue, 17 Dec 2024 02:32:19 +1100
>  > a) Shouldnt the strftime() call return "14:32:19 +1100" - which would fix
>  > the when_written value. (The message renders with a "written 12hrs ago"
>  > statement).

I'm still wondering why strftime() is still returning an invalid time - out by the timezone plus 1 hr?


...����

---
� Synchronet � AnsiTEX bringing back videotex but with ANSI

You are viewing proxied material from cvs.synchro.net. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.