Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » U++ Library support » U++ Core » Date limited to 2020 and 2015 does not work ?!?
Re: Date limited to 2020 and 2015 does not work ?!? [message #30063 is a reply to message #30062] Mon, 06 December 2010 10:02 Go to previous message
mirek is currently offline  mirek
Messages: 14255
Registered: November 2005
Ultimate Member
mr_ped wrote on Mon, 06 December 2010 03:10

mirek wrote on Sat, 04 December 2010 20:07

mr_ped wrote on Fri, 03 December 2010 04:17

Yep, I would suggest to remove the fallback completely.
(i.e. 20 is really year 20 A.D., not 1920 or 2020)

I think anybody sane already moved to 4 digit year, and others should finally fix their apps, so why not to force them.


Actually, it is more about comfort when entering dates into EditDate..



Yes, but that should be in "presenter" layer IMHO, it's not related to actual datetime type. So in U++ it should be part of EditDate control right in the UI related code, anything more deeper should work with full year. There's another spot in code where it may be handy, during import of external data. Otherwise I think the time_t and 4 digit string is the only acceptable form to work with date internally.


Well, you might be right - but that means splitting the Convert for Date/Time into two ('presentation' and 'core')...

Mirek

 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: HELPER: Value grouping to ValueArray
Next Topic: NEW: generic Toupel grouper
Goto Forum:
  


Current Time: Sun Apr 27 23:36:45 CEST 2025

Total time taken to generate the page: 0.00484 seconds