Bug? "Export As Zip" changes date of zipped files

[Widget]

I noticed if I do a "File > Export As Zip", the "Date Modified" date of the files in the zip will all be set to the time they were zipped. Why? It shouldn't do this because when I extract the files they all have the same modified date (when they were zipped) and I can't tell if these unzipped files are newer or older than my current set of files for the same project. In other words, the "Export As Zip" should not change the last modified date of the files stored in the zip file.

TIA

 

[Widget]

This is still a major problem. I had to restore a set of files that were zipped yesterday using "Export as Zip". But the files that were restored from the zip file now all have the same datestamp, namely yesterday's date/time in which they were zipped. Why? Why change the file's modify date & time when you are backing up files? I have another set of these files elsewhere on my hard disk but now I can't tell which file is more recent. I have ended up with a dog's breakfast.

Please don't change the datestamp for the files when they are backed up using "File > Export as Zip". Otherwise it renders this tool useless.
TIA

 

[Erel]

It does preserve the time in the latest version of B4A.

 

[Widget]

It does preserve the time in the latest version of B4A.

I'm using B4A v7.80 and I just tried it now and it marks all of the *.bas files in the zip (from SharedModules directory) with the modified date of when "Export as Zip" was run.

The other files in the zip like *.b4a and the files under Files directory and Objects directory do not have their timestamps changed. So it looks like B4A is copying the SharedModule files to a temporary directory and then zipping up that directory, which is probably how these files get their timestamp changed. Is there a way to preserve the timestamp of these SharedModule files?

TIA

 

[Erel]

Is there a way to preserve the timestamp of these SharedModule files?

Currently no. It will be fixed.