Right. I tried it and it works almost fine!RomCenter wrote:Yes, and as it is not critical, I will keep this for the next version.Wanderer wrote:- When trying to create a new database, if the database exists, RC just reports that it exists and stops instead of asking whether you wish to overwrite the database (as one would expect).
If you want to keep the same name, you can do an 'update' instead of a new. 'update' will also keep your settings and roms paths.
Only one thing is not done. The name of the database that exists in the "datafile" tree branch is not updated. Closing and reopening RC does not help, the old name is still shown.I see. It is a little puzzling but i get it. While testing this though, i found something which should not happen. Even without having opened any rom path, when clicking on "rom files", some of the buttons in the button bar are enabled as if a path existed. There, the user is able to click on "fix" which actually starts the fix process but it is unclear what RC is doing in that case. Perhaps it creates the bad dumps but where does it store them?RomCenter wrote:It is correct.Wanderer wrote:- I just created a new database from mame 0.124a. Before having a chance to add a rom path, i noticed that at the status bar it is reported that i have one green and three yellow roms! In the database filters i have set RC to show only green and yellow roms. Opening the "All games (flat)" branch, there are three roms and a bios in there in yellow color, all of them containing bad dumps! This looks like a bug.
mac2bios contains 2 bad dumped bioses roms which can be created by romcenter.
comebaby contains a chd and a rom. The chd is missing, but the rom can also be created by romcenter (bad dump) -> yellow because partially available.
Same for ddrja and ddrjb.
Aha, now i see the logic behind it. Yes, this is logical in roms branches, where there may be an existing "original" rom or an existing bios associated with a rom, but in the bioses branch where there are no other associated files with them? If some roms exist in a bios but some others are missing, shouldn't it be yellow denoting that "you need to download something, but not all file"?RomCenter wrote:Like in rc2 ? I think about the icons color, and, with bios, samples, chd, roms and merged icons, I decided to do it that way. It is more clear and there was not enough differences between a yellow and red icon in rc2, in both cases, you need to download the ro, again. Now, if one rom is missing, it is red. If one of above rom 'category' is green (ie all samples are available for example), the game is yellow. It means you need to download something, but not all file. Maybe just bios, or main set, or chd.Wanderer wrote:- When some roms are missing from a bios zip file, the bios under the "bios files" database branch is shown in red color. Wouldn't yellow be more proper? It could perhaps be red if no roms existed at all (no zip file) and yellow if some roms existed but some were missing.
Anyway, this is a matter of definition. I think the logic behind that is rather complicated for plain users to follow. Personally, i mostly care about the colors in the "rom path" branch but for some reason, the red color in bioses with some (not all) missing roms seemed a little inconsistent to me.
At first i assumed i had gone blind but that's not the case. Remember the bug where RC window was maximized but when closing and reopening RC, the window didn't appear at the top of the screen? It's back again. Funny though, it happens in a WinXP SP2 PC, i'm looking at it right now but i'm not so sure it happened in my other PC (Win2K) yesterday.RomCenter wrote:This number is available in the main status bar.Wanderer wrote:- It would be nice to be able to see the number of contained roms of database branches (i.e. "Original", "Clones, etc) when clicking on them. Perhaps in the space above the right list, where also the rom paths totals are shown...
It will take some time to get used to the new stuff...