[Coco] VCC Update
James Ross
jrosslist at outlook.com
Fri Apr 14 15:03:18 EDT 2017
Bill and Luis, how about this as a compromise:
Virtual Hardware (*.dll)
Program Packs (*.ccc, *.pak, *.rom)
All Files (*.*)
So that away, there is a clear distinction between a ROM file, regardless the extension or a piece of hardware attached. That might clear up the difference between the two kinds?
Luis, the thing about using "Cartridges" by itself is that some carts (sound, etc...) would actually fall into the Virtual Hardware category.
That was actually confusing to me at first, a while back, that you could load DLL's -- so for some time, I couldn't understand what happened to my MPI and then I would go directly to the *.INI file and fix it there.
I still need to check if VCC already knows what do w/ the other extensions ... and the any file option would have to equate to being a ROM file as well.
________________________________________
From: Coco <coco-bounces at maltedmedia.com> on behalf of Luis Fernández <luis46coco at hotmail.com>
I would like to propose:
The virtual hardware should be called: instead of Program Paks, would it be, virtual hardware, would you agree?
Not integrated, I propose
Virtual Hardware (*.rom, *.dll)
Cartridges (*.ccc, *.pak)
All Files (*.*)
________________________________
De: Coco <coco-bounces at maltedmedia.com> en nombre de Bill Pierce via Coco <coco at maltedmedia.com>
This looks cool James, It's something I've complained about since I first ran VCC back when Joseph was developing it.
BTW, Luis's patch could very well just include both sets in one line. There's not need to differentiate the types as they're all the same (except dll). It would get confusing to some. I.E. "Program Packs(*.ROM,*.DLL,*.ccc,*.pak)
More information about the Coco
mailing list