Updated Unix Timestamp Converter

[niyari]

Pull request type

Please check the type of change your PR introduces:

• Bugfix
• Feature
• UI change (please include screenshot!)
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no api changes)
• Build related changes
• Documentation content changes
• Internationalization and localization
• Other (please describe):

What is the current behavior?

Issue Number: #473

What is the new behavior?

• Time zone support.
• Support for time carry forward and backward.
• Resolved performance degradation that occurs when values are out of range.

Other information

• Conflict with the addition of a Now button needs to be resolved.

Quality check

Before creating this PR, have you:

• Followed the code style guideline as described in CONTRIBUTING.md
• Verified that the change work in Release build configuration
• Checked all unit tests pass

[niyari]

Looks good to display in text, InfoBar can be removed.
Timestamp to .NET Ticks (If features are to be added here.) #512

[veler]

Hello :)
Thank you for getting the PR up, and sorry for the late answer.

A few remarks on the screenshot you shared:

The following info is great, but they visually don't align with the rest of the UI on the left:

Suggestion:

What about putting this info either below the Time Zone or Year Month Day... input?
Additionally, perhaps it could be place into a Grid with a lighter background color, like through this style:

https://github.com/veler/DevToys/blob/b11f267ef738501bbf993c677013777cb764b1aa/src/dev/impl/DevToys/Views/Tools/Graphic/ColorBlindnessSimulator/ImagePreview.xaml#L12-L23

Which looks like this:

Or even, an expandable container, like in the setting page:

Here is how it's made:
https://github.com/veler/DevToys/blob/da659990b1185011edb8182ad340e37e6b5f6611/src/dev/impl/DevToys/Views/Tools/Settings/SettingsToolPage.xaml#L142-L165

What do you think? :)

Thank you !

[niyari]

Timezone info UI is derived from the Text Case Converter.
Of the suggestions for unifying visual information, we have 3 candidates.
expandable container hides much needed information for users living in areas that do not use daylight savings time.

In the case of A and B, B is usually more compact on the screen.
However, DevToys is expected to be used primarily with some kind of work.
In order for DevToys to be a viable tool with the smallest screen size, all the operable items need to be gathered at the top.

It would be best if the screen layout could be changed according to the window size like on the web, but first we would like to display it at the bottom of the C plan.

[veler]

Hello,

Thanks for your quick answer :)

I like A plan better!
Although you are right, either plan A, B or C, there is an issue with Compact Mode.
Good thing is, by using VisualState, we can actually change the layout on Compact Mode. We do something like this for TextDiff tool:
https://github.com/veler/DevToys/blob/b11f267ef738501bbf993c677013777cb764b1aa/src/dev/impl/DevToys/Views/Tools/Text/TextDiff/TextDiffToolPage.xaml#L14-L30

We hide the input fields and for this, we have to change a bit the layout so it resize accordingly. Perhaps we can do the same here so some information displayed horizontally turn to be displayed vertically?

[niyari]

Responsive (changes with window width) is going to be better regardless of mode.
I would like to make this a separate PR, what do you think?

Furthermore, I found that after changing to compact mode, changing the window size causes the application to stop.
I will submit a new issue.

[veler]

Hello,
Thanks for your answer. I'm fine with addressing that in another PR, perhaps I can even do that myself later.
There are some merge conflict in this PR apparently :)

[niyari]

How about this?(use AdaptiveTrigger)

[veler]

How about this?(use AdaptiveTrigger)

I like that better! In particular the year/month/day going on a second line.
I find a bit more weird, however, that the time zone information is jumping from above year/month/day to below year/month/day.

[niyari]

I think this will work.

[veler]

Can we keep the TimeZone information just below the TimeZone combo box?

[niyari]

In commit c3027e0, the Timezone combo box is back to fixed.

[veler]

I looked at the PR, built the branch and played with it. It looks very good overall 😁 Good job! Just a few details and here and there and we can merge this awesome PR! 😁

[veler]

It looks good now! :D Thank you very much for this great pull request! I appreciate your contribution a lot! :D