Carenado Cessna 340II

Every time I check my account I'm told there is new update available and when I d/l it it's same. There is a problem somewhere.....sorry guy's.


Dick
 
The service pack number "20110126" could be slightly confusing at first. It looks like it would be a version "2", until you realize it's just the release date in a backwards format "01-26-2011".

FAC
 
The service pack number "20110126" could be slightly confusing at first. It looks like it would be a version "2", until you realize it's just the release date in a backwards format "01-26-2011".

FAC

I think most of the rest of the world would point out that we Americans are a little backwards to write it "1/26/2011". Year-month-day makes more sense from a strictly logical perspective.
 
I think most of the rest of the world would point out that we Americans are a little backwards to write it "1/26/2011". Year-month-day makes more sense from a strictly logical perspective.

You know Bill, this thread has caused me to "rethink" my own versioning system. I've been using a "build date" as the decimal part of my versioning, but have been using "ddmmyy..."

This has resulted in more than one person questioning "which is the latest version?" over the past few months.

By switching to a "yymmdd" format, it should be more clear to everyone which is the latest version! :ernae:

For example:

MilViz_C310R_v1.092310 would become MilViz_C310R_v1.100923
MilViz_C310R_v1.012011 would become MilViz_C310R_v1.110120

Since "everyone knows" that "09xxxx" is greater than "01xxxx" naturally there has been some confusion! What was clear to me certainly wasn't clear to anyone else! <INSERT here blush>

So! Thanks to everyone for helping this old man "wake up and smell the coffee..." :173go1:
 
Back
Top