I’ve noticed that if a series is saved with a dot in the filename, the actual filename used excludes everything after the dot.
For example, save as “MySeries.v1” gives an actual filename of “MySeries.blw”.
So if you make some changes, then save as “MySeries.v2”, it is also saved as “MySeries.blw”, overwriting the previous version without a warning.
I guess there’s some code that thinks the v1/v2 is a file extension, so changes it to “blw”. Could this be changed?
I wouldn’t recommend using a dot in a filename - it is much safer to use either a hypen “-”, Underscore “_” or a space. - Jon
I wouldn’t recommend using a dot in a file name. It is better to use either a hyphen “-”, underscore “_” or space - Jon
Sender notified by
[Mailtrack](https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&)
17/09/18, 15:50:06
···
Jon Eskdale
03333 443377
07530 112233
Try using an underscore or other acceptable non alpha numeric character in place of the dot in your filenames. Eg. myfilename_v1.blw
···
From: sailwave@yahoogroups.com [mailto:sailwave@yahoogroups.com]
Sent: 17 September 2018 09:40
To: sailwave@yahoogroups.com
Subject: [sailwave] Dot in “Save as” filename
I’ve noticed that if a series is saved with a dot in the filename, the actual filename used excludes everything after the dot.
For example, save as “MySeries.v1” gives an actual filename of “MySeries.blw”.
So if you make some changes, then save as “MySeries.v2”, it is also saved as “MySeries.blw”, overwriting the previous version without a warning.
I guess there’s some code that thinks the v1/v2 is a file extension, so changes it to “blw”. Could this be changed?
I wouldn’t recommend using a dot in a file name. It is better to use either a hyphen “-”, underscore “_” or space - Jon
A ‘dot’ has a special meaning when it comes to filenames and normally denotes the beginning of the file type or extension. Remember CPM and MS-DOS!
Sailwave won’t be the only system that does as you’ve experienced. I avoid a ‘dot’ and ordinarily use a space or very occasionally another character acceptable as part of the filename in these situations.
···
Richard
Win the original handcrafted Black Isle Bowl from the Black Isle Men’s Shed. Go to http://bimshed.uk/bowl.asp for full details.
I’m a bit surprised by these responses! Having 2 dots is perfectly legal in Windows filenames - just have a look in c:\ and I bet you have a whole lot of “eula.9999.txt” filenames. And any .net app will have an application.exe.config file!
It’s a simple change - just set the SaveFileDialog’s SupportMultiDottedExtensions property true and problem solved.
I would think that this is an operating system quirk, not Sailwave’s
program.
Better to use something else - +, _ ! etc.
···
regards,
Malcolm Osborne
Rondevlei, South Africa
On 2018-09-17 10:40,
[sailwave] wrote:
I've noticed that if a series is saved with a dot
in the filename, the actual filename used excludes
everything after the dot.
For example, save as "MySeries.v1" gives an actual
filename of “MySeries.blw”.
So if you make some changes, then save as
“MySeries.v2”, it is also saved as “MySeries.blw”,
overwriting the previous version without a warning.
I guess there's some code that thinks the v1/v2 is a
file extension, so changes it to “blw”. Could this be
changed?
This email has been checked for viruses by Avast antivirus software.
www.avast.com
geoff.turner@parkerseal.org.uk
Hi Geoff,
Wouldn’t it be nice if life was that simple. Yes two dots are now valid in a Windows file name but they didn’t use to be. It’s not a Dot Net app its written in Clarion so some things are not as easy to do as they would be in Dot Net but on the other hand, it produces very efficient code with no need for runtime libraries and works well under wine on linux and Apple Mac’s . And the code size is incredibly compact.
Its not just a case of saving the file and allowing the two dots as Sailwave and other applications that read the files also need to be able to handle filenames with two dots which we can’t guarantee that they could. Also, code within Sailwave for stripping paths and filenames would all need modification. So as I said previously it is far better to use a - _ or space which solves all the problems and allows for greater compatibility and in my opinion better readability. - Jon
Sender notified by
[Mailtrack](https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality6&) 18/09/18, 14:30:37
···
Jon Eskdale
03333 443377
07530 112233
Thanks for that response!
In fact, the “.” wasn’t entered on purpose. It happened like this:
-
The user decided to split the series into 2 separate series.
-
Went into “Save As”, backspaced to delete the “blw” and entered “GH”, inadvertently leaving the “.”. So the filename read “MySeries.GH” instead of the intended “MySeriesGH”
-
Deleted all the GH (general handicap) competitors
-
Saved as “MySeries.blw”
-
Tried to open “MySeries.GH” - but it’s not there. And so all the deleted competitors needed to be re-entered.
Is there any way that “Save as” could at least give a warning if a file’s being overwritten?