Literal operators showing incorrect results

[anmac1789]

Using this syntax I can see there is a time difference

Code: Select all

addcolumn:column1;column2 column1:=$dc:.."-"..$dm:.."=" column2:=$dm:-$dc: pic: dm:2022-10-2T18:24:41 dm:!=dc:

Screenshot 2023-01-20 141820.jpg (78.53 KiB) Viewed 1070 times

date created ‎October ‎2, ‎2022, ‏‎6:24:41 PM
date modified ‎October ‎2, ‎2022, ‏‎6:24:41 PM

I understand that using ticks gives an accurate description of time with greater precision but how can I change the time resolution to accuracy of exact second such as 41 seconds and nothing smaller than that. How can I change it so that when using dc:!=dm: the result above won't show ? Thanks

[void]

Currently, you'll need to save to a custom column and compare, for example:

addcolumn:column1;column2 column1:=$dm:/10000000 column2:=$dc:/10000000 column1:!=column2:

/10000000 will convert the FILETIME from 100-nano-seconds to seconds.



I'll make this easier in the next alpha update with:

eval:$dm:/10000000!=$dc:/10000000



There's also daymodified:!=daycreated: | timemodified:!=timecreated:

daymodified/daycreated is the date part only.

timemodified/timecreated have a resolution of milliseconds.



Maybe Everything needs more properties here?
eg: dm-as-seconds:!=dc-as-seconds:

[anmac1789]

I think that will be worthwhile to have. Can you test it on your end and see how useful it is?

Btw, how do I find no duplicates of a single custom column1 ? Is it unique: or distinct: ?

[void]

Everything 1.5.0.1336a improves the eval: search function.

The eval: function now uses column formulas instead of the preprocessor.

The search matches when the eval expression evaluates as true or non-zero.



For example, to compare date modified as seconds to date created as seconds:

eval:$dm:/10000000==$dc:/10000000



I am still considering dm-as-seconds:/dc-as-seconds:

[anmac1789]

Hi, thanks for following up with this. I will test this out. I think something more specific will be more useful to the average joe since typo's can come about when converting between 100 nanoseconds to human-readable seconds..

Btw, is it possible to "See" the evaluation expression in a custom column?