RetroFE development

[Pieter Hulshoff]

Here's a Windows build for 0.7.20b4.
-----
Changes:
- Support for multiple rompaths using the ; separator for list.path in the collection's settings.conf
- Removed requirement for the presence of the collection's settings.conf file.
- Recreated meta.db whenever any of the meta files or the executable changes.
- Support for launchers per game via the directory collections/collection name/launchers/game name.conf
- Support for multiple keys for the same action in controls.conf, comma separated (catelite)
- Improved video performance and playback, including aspect ratio (PinealServo)
- Improvement of input handlers (PinealServo)
- Support for launchers per OS via the optional launcher directories launchers.linux, launchers.windows, and launchers.apple
- Enable gdb debugging symbols in debug build for non-Windows (PinealServo)
- Fix crash when launcher files don't have extensions (PinealServo)
-----
As always: this is WIP, so please back up your working retrofe.exe before installing this one so you can go back if this one doesn't work for you. Let me know if you encounter any problems; I'd like to release 0.7.20 as full release before too long if there are no serious bugs.

[ryuuji]

Cool. Looks like the video brightness is fixed now  . Thanks.

[PinealServo]

Cool; the brightness change was probably an artifact of the conversion from a planar YUV 4:2:0 to a packed YUV 4:2:2 pixel format that was previously going on, or maybe an artifact of how SDL sets up the pixel shaders that convert the resulting textures of the two formats into RGB video frames. I wasn't sure it would fix that issue, but I'm glad it did!

[PinealServo]

I've been playing around with a very cool feature of gcc, which is the set of "sanitizer" tools it has built-in now. If you're familiar with valgrind, it can catch many of the same kinds of errors but the program runs a *lot* faster than it does under valgrind and seems to do a better job of pinpointing where the relevant objects are referenced in the source.

Anyway, with -fsanitize=address and valgrind, I found a few little things that could potentially cause problems. These include some uninitialized variables being accessed, some memory being accessed after it was freed, and a *lot* of little memory leaks.

A bunch of the memory leaks are in the animation system and I haven't figured out where to free things yet, but I've fixed a bunch of the other problems.  I'll have a pull request coming for those misc clean-ups soon.

[Pieter Hulshoff]

Good work. I'll pull it in for 0.7.20b5 then.

[GoodWill Emu]

I made a pre-Alpha of a RetroFE Setup Tool!

It has no actual Functionality, only opening windows and  quitting, but I would like to know what you think.

It's a python source file, just open it with a Python 3.6 Compiler.

[johnsaints]

Just replace the .exe in "core" folder and it's ready ?

[Pieter Hulshoff]

Just replace the .exe in "core" folder and it's ready ?

You mean the beta versions of RetroFE? Yes, that's sufficient.

[johnsaints]

It did not work for me. I separated the two paths with ";", but the program only reads the first path. =/

[Pieter Hulshoff]

Post your log.txt, please?

[johnsaints]

Here. Thanks.

[Pieter Hulshoff]

Try removing the space after the ;
I don't think I considered removing whitespace from the path...

[Tom Acunzo]

Hi Pieter MacOS ran fine on the initial tests including pngs I'll update brew on my tap to make the retrofe install live for Mac on the new branch. I also may need to update the readme notes as they differ with recent changes. I'll keep you posted.

[johnsaints]

Try removing the space after the ;
I don't think I considered removing whitespace from the path...

Thanks Sir, the space was the problem. Now it's working. Good Job. 

[Pieter Hulshoff]

Here's RetroFE 0.7.21b1:
- Fixed support for "Shift Left" in controls.conf
- Fixed support for onMenuEnter="0" for 2nd level menu and similar theme features
Thanks PinealServo for your help.