[Valentina] Re: Vdb files

[Keith DeLong]

>> Carbon apps can have both a type/creator and extension. What is the problem?
> 
> Keith, that was my scream. :->

Hi Jon,
 
> I have absolutely no problem if anyone wants to use extensions in OS
> X. But I don't see why they have to be forced on us! They can be
> supported on an app-by-app basis. What I saw was that with 1.9.7b5,
> all of a sudden I couldn't open any of my existing databases (this
> using V4RB). 

Somehow I missed the context...

> Moreover, to make them compatible I would have to add a
> ".vdb" extension, which would confuse my users no end (my
> application's name doesn't begin with a "v", for starters).

This is exactly why Rulsan added ValentinaSetExtensions. Just before the
create, setting the extensions allows you to have and extension you want for
the data, blob, dat, and indexes. This is what I was trying to use.
Currently, ValentinaSetExtensions "vtc", "dat, "blb", "ind" works on evey
file except the .vtc file. This is ignored by the ValentinaSetExtensions
command.

So, if you ever want to release an OS X or Windows version, you'll need to
add an extension for the file type to be properly associated by the OS.

An unexpected side benefit has occurred in customer support. When I ask a
user to find their data file, they often cannot remember its name or
location. I have them do a search on *.vtc (my data file extension) and we
find the data file right away.
 
> Hence the scream.
> 
> Making extension a developer option, as you are asking for, would be
> perfectly fine.

We're on the same page...
 
Keith