BINGO!! - Correct - ahhh, but too logical. So let's see, you sell the product as X365, DUH - doesn't it make sense to include this everywhere?
Now as for the version number (return to my pix in post #1 in this thread) - it makes greater sense to dump "12" and use the last two digits of the year: "16", etc. Going forward, the version will definitively portray when it was released. Too tough to do? At least replace "12" w/ "16". Easy. SO - why not just do it?
FYI - Every website's "File Save As" I do has this, as applicable (re. RWD & X365), in my saved file format: "<customer>_2016-07-20_v000-RWD-X365". the version number increments with every save I do which is FREQUENT. This file instantly & redundantly saves off to two servers. The next day the file name's date gets updated and the version gets reset to 000. BTW, v000 today is an exact copy of the last saved file from the day prior. One more layer to try to goof proof things - such as when you do a Save vs. File Save as - GULP!
If I can do this, why can't Xara?
I have had way, way, way too many tech support calls and emails regarding all sorts of CAD software to the factories in India - and it is my opinion the left and right hands have little clue what each is doing. Why? ZERO Management and ZERO effective QA. Consequently you end up with a plethora of inconsistencies - even to the point where you cannot correlate two conjoined actions. A good example: ORCAD Schematic Capture software. HP printers is another - w/ one problem - I logged 44 hours on the phone in several days - so bad I'll never EVER buy anything HP again. Another w/ Dell re. how to rotate monitors from landscape to portrait. No one had a clue. I wrote a tech article after I finally figured it out and posted it on a Dell forum.
So is Xara going down the very long disjointed road those in India seem to have been doing for YEARS (IMO)?
Bookmarks