Offsets from logs not working

[Falco20019]

Describe the bug

If you open a log file with a different (non-UTC) timestamp, it's lost during usage.

ℹ Computer information

• OS: Windows 10 Version 22H2 64 bit
• Analogy Version: 7.2.0 .NET 8
• Data Provider: Serilog

📝 Provide detailed reproduction steps (if any)

1. Configure DateTimePattern with yyyy.MM.dd HH:mm:ss.fff zzz
2. Import the logfile example1.txt as .clef using Serilog Parser
3. See that the timestamps are messed up to have your own timezone instead of the one from the logs

✔️ Expected result

First entry should show 2016.10.12 04:46:58.055 +03:00

❌ Actual result

First entry shows 2016.10.12 04:46:58.055 +02:00 (or whatever your own timezone is)
It's not recalculated, it's just using UTC and messes the timezone

📷 Screenshots

[Falco20019]

I assume it's converted from a DateTimeOffset into a DateTime somewhere which usually uses DateTimeKind.Unspecified and therefore shows the local time zone when formatted. At least that's a common issue I've seen a lot.

[LiorBanai]

Correct. It is converted to DateTime. Working on a fix.

[LiorBanai]

supports of DateTimeOffset at provider level was added and merge into main branch.
Next step: Adding at UI level. Some issue with sql filtering.
Still work in progress

[LiorBanai]

UI is updated correctly.
only existing issue is the sql filter fails on DataTimeOffset..