Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Shorten date faceplate display #22

Open
MatthewScholefield opened this issue Mar 5, 2018 · 5 comments
Open

Shorten date faceplate display #22

MatthewScholefield opened this issue Mar 5, 2018 · 5 comments

Comments

@MatthewScholefield
Copy link
Collaborator

If we change 3/5/2018 to 3/5/18 I think it will fit without scrolling.

@MrGrymReaper
Copy link

MrGrymReaper commented Mar 18, 2018

@MatthewScholefield Is this for just displaying the date or will that be for other uses when accessed by skills?

Have you heard of the "Millenium Bug" which necessitated an update for a wide variety of devices (including computers). Due to problems caused by using dates with only two digit years (80-99) instead of four digit years (1980-1999). With the previous past year 2000 and previous 2 digit years and badly thought out software's year support. Software which was date/time sensitive had problems handling the event and working how they were, supposed to when designed.

As well as the size of the undertaking required to perform the fixing of the issue in the first place.

Read the article from Wikipedia (https://en.wikipedia.org/wiki/Year_2000_problem) or Britannica (https://www.britannica.com/technology/Y2K-bug).

You want to go back to having a 2 digit year and potentially need to do the patching all over again when the next millennium rolls around! Wasting yet more time having to make another fix for the same issue where 4 digit year and an adjustment on valid years range would save time and other resources.

@MatthewScholefield
Copy link
Collaborator Author

The faceplate display is a totally separate function that won't affect anything else, so no worries :).

@MrGrymReaper
Copy link

@MatthewScholefield Can you guarantee that it will remain this way if the change is implemented? That it won't be affected (or affect anything in future)?

@MatthewScholefield
Copy link
Collaborator Author

Yes I can.

@MrGrymReaper
Copy link

@MatthewScholefield Then I don't mind too much. As long as it doesn't confuse people too much when another new millennium comes along.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants