1
Announcements / Re: RetroFE development
« on: February 08, 2017, 08:47:47 PM »
All my themes are broken. 
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
2
Announcements / Re: RetroFE development
« on: February 05, 2017, 07:23:19 PM »
It's a bit redundant, 0.x.y is all beta until 1.0 and beyond is out right?
3
Share your theme / Where can I get an updated Carousel 16x9?
« on: February 02, 2017, 05:15:21 PM »
Just wondering if the older themes are being migrated over?
Thanks.
Thanks.
4
Announcements / Re: RetroFE development
« on: February 01, 2017, 11:05:16 PM »
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.
5
Announcements / Re: New features
« on: January 09, 2017, 12:49:19 AM »
The fix works well. Thanks Pieter.
6
Announcements / Re: New features
« on: January 08, 2017, 05:39:55 PM »
I think the issue is that CollectionInfoBuilder is expecting a roms folder inside collections/Main which isn't there for any OS.
This is why you should run the python post install step and test new retrofe changes from inside Artifacts. There will be fresh installations of retrofe that don't have Mame even set up yet.
It's also good to double check once you copy files or folders to Package/Environment/<OS>
or if you add roms to Package/Environment/Common/collections/Main/ in bitbucket.
Hence my whole don't forget comment from before as a sanity check for new features.
UPDATE - The spacebar key event loop is tested good. Retrofe loads after creating the roms folder.
This is why you should run the python post install step and test new retrofe changes from inside Artifacts. There will be fresh installations of retrofe that don't have Mame even set up yet.
It's also good to double check once you copy files or folders to Package/Environment/<OS>
or if you add roms to Package/Environment/Common/collections/Main/ in bitbucket.
Hence my whole don't forget comment from before as a sanity check for new features.
UPDATE - The spacebar key event loop is tested good. Retrofe loads after creating the roms folder.
7
Announcements / Re: New features
« on: January 08, 2017, 04:33:17 PM »I thought I'd give an overview of the new features since 0.7.19 that were included in 0.7.20b1 (http://retrofe.nl/SMF/index.php?topic=7.msg291#msg291):And:
- Fixed menuSort = no behavior for include.txt files.
- Fixed Windows expansion of %RETROFE_EXEC_PATH%.
- Fixed local language support.
- Fixed container scaling.
- Fixed input queue when returning from a game.
- Fixed crash on exit when a controller is connected.
- Rewritten menu scrolling and input handler.
- Added support for hierarchy in the roms directory via list.romHierarchy parameter in collection's settings.conf file.
- Added playlist support via the keys favPlaylist, nextPlaylist, and prevPlaylist. The playlists should be placed as <playlist name>.txt in the collections/<collection name>/playlists directory.
- Added MacOS support (Tom).
- Fixed incorrect sRGB profile errors for PNGs
- Added support for /home/user/.retrofe RETROFE_PATH setting for linux / mac.
- Added brew install option for mac
- Updated Overview instructions in readme
Note: The last two will be tweaked again via pull request.
Latest changes still break Mac (See CollectionInfoBuilder::ImportRomDirectory), haven't tested other builds.
Code: [Select]
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_pthread.dylib 0x00007fff94f184fc pthread_mutex_lock + 0
1 libsystem_c.dylib 0x00007fff94d5e9f8 closedir + 25
2 retrofe 0x00000001040bc777 CollectionInfoBuilder::ImportRomDirectory(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, CollectionInfo*, std::__1::map<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, Item*, std::__1::less<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > >, std::__1::allocator<std::__1::pair<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const, Item*> > >, std::__1::map<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, Item*, std::__1::less<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > >, std::__1::allocator<std::__1::pair<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const, Item*> > >, bool) + 805
3 retrofe 0x00000001040bb2bd CollectionInfoBuilder::ImportDirectory(CollectionInfo*, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >) + 2255
4 retrofe 0x00000001040ba5b8 CollectionInfoBuilder::buildCollection(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >) + 1674
5 retrofe 0x00000001040b9ee4 CollectionInfoBuilder::buildCollection(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >) + 72
6 retrofe 0x00000001040f7829 RetroFE::getCollection(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >) + 75
7 retrofe 0x00000001040f6028 RetroFE::run() + 2622
8 retrofe 0x00000001040f43ac main + 5788
9 libdyld.dylib 0x00007fff94d03255 start + 1
8
Announcements / Re: New features
« on: January 07, 2017, 08:39:24 PM »
It's not so much as a mac issue per say (incorrect sRGB profile). A newer version of libpng is out. They have included some tools to patch pngs. I think they may suppress the error warnings in the library as other projects complained about how verbose they were and some apps even crashed. As for RetroFE it just spewed messages to the console every time an image was loaded.
The files that I did patch in bitbucket I used a tool pngcrush.
But it's funny you brought it. Libpng literally just patched a huge 21 year old vulernabilty in 1.6.27! Totally worth a read on there main page as it may seriously affect people in different ways.
Toms-MacBook-Pro:sfml Tom$ brew info libpng
libpng: stable 1.6.26 (bottled), HEAD
Library for manipulating PNG images
http://www.libpng.org/pub/png/libpng.html
/usr/local/Cellar/libpng/1.6.26 (26 files, 1.2M) *
Poured from bottle on 2016-12-16 at 22:06:15
From: https://github.com/Homebrew/homebrew-core/blob/master/Formula/libpng.rb
==> Options
--universal
Build a universal binary
--HEAD
Install HEAD version
Toms-MacBook-Pro:sfml Tom$ brew list libpng
/usr/local/Cellar/libpng/1.6.26/bin/libpng-config
/usr/local/Cellar/libpng/1.6.26/bin/libpng16-config
/usr/local/Cellar/libpng/1.6.26/bin/png-fix-itxt
/usr/local/Cellar/libpng/1.6.26/bin/pngfix
/usr/local/Cellar/libpng/1.6.26/include/libpng16/ (3 files)
/usr/local/Cellar/libpng/1.6.26/include/ (3 files)
/usr/local/Cellar/libpng/1.6.26/lib/libpng16.16.dylib
/usr/local/Cellar/libpng/1.6.26/lib/pkgconfig/ (2 files)
/usr/local/Cellar/libpng/1.6.26/lib/ (4 other files)
/usr/local/Cellar/libpng/1.6.26/share/man/ (3 files)
Update: I went a little overboard, the exploit is nothing major to us.
The files that I did patch in bitbucket I used a tool pngcrush.
But it's funny you brought it. Libpng literally just patched a huge 21 year old vulernabilty in 1.6.27! Totally worth a read on there main page as it may seriously affect people in different ways.
Toms-MacBook-Pro:sfml Tom$ brew info libpng
libpng: stable 1.6.26 (bottled), HEAD
Library for manipulating PNG images
http://www.libpng.org/pub/png/libpng.html
/usr/local/Cellar/libpng/1.6.26 (26 files, 1.2M) *
Poured from bottle on 2016-12-16 at 22:06:15
From: https://github.com/Homebrew/homebrew-core/blob/master/Formula/libpng.rb
==> Options
--universal
Build a universal binary
--HEAD
Install HEAD version
Toms-MacBook-Pro:sfml Tom$ brew list libpng
/usr/local/Cellar/libpng/1.6.26/bin/libpng-config
/usr/local/Cellar/libpng/1.6.26/bin/libpng16-config
/usr/local/Cellar/libpng/1.6.26/bin/png-fix-itxt
/usr/local/Cellar/libpng/1.6.26/bin/pngfix
/usr/local/Cellar/libpng/1.6.26/include/libpng16/ (3 files)
/usr/local/Cellar/libpng/1.6.26/include/ (3 files)
/usr/local/Cellar/libpng/1.6.26/lib/libpng16.16.dylib
/usr/local/Cellar/libpng/1.6.26/lib/pkgconfig/ (2 files)
/usr/local/Cellar/libpng/1.6.26/lib/ (4 other files)
/usr/local/Cellar/libpng/1.6.26/share/man/ (3 files)
Update: I went a little overboard, the exploit is nothing major to us.
9
Announcements / Re: New features
« on: January 07, 2017, 07:22:25 PM »and don't forget there is now a --os=mac option for running the python step. We should better track adding new features as they affect multiple platforms.In this case I just didn't test it fully enough; it's not OS related. I added playlists, and only tested it with collections that actually had playlists, including my Main collection.
Sent from my SM-G920F using Tapatalk
In case new file types are added to collections or whatever in the future and the post script copies those to Artifacts. Yes otherwise error checking is nice.
10
Announcements / Re: New features
« on: January 07, 2017, 05:03:30 PM »
and don't forget there is now a --os=mac option for running the python step. We should better track adding new features as they affect multiple platforms.
11
Announcements / Re: New features
« on: January 07, 2017, 04:50:01 PM »
I've only tested mac via quick brew install. Can't put much more time into it today. Something about adding playlists inside CollectionInfoBuilder
Code: [Select]
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_pthread.dylib 0x00007fffd61e04fc pthread_mutex_lock + 0
1 libsystem_c.dylib 0x00007fffd602dadc readdir$INODE64 + 22
2 retrofe 0x0000000104e14e5f CollectionInfoBuilder::addPlaylists(CollectionInfo*) + 277
3 retrofe 0x0000000104e4fc54 RetroFE::getCollection(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >) + 1078
4 retrofe 0x0000000104e4e068 RetroFE::run() + 2622
5 retrofe 0x0000000104e4c3ec main + 5788
6 libdyld.dylib 0x00007fffd5fcb255 start + 1
12
Announcements / Re: New features
« on: January 07, 2017, 04:29:46 PM »
I get Segmentation fault: 11...
If I advance the Load screen with spacebar or don't let it play to the end or even if I hit escape to quit before the load screen finishes all result in a crash.
added note:
$ retrofe --version
RetroFE version 0.7.20b1
If I advance the Load screen with spacebar or don't let it play to the end or even if I hit escape to quit before the load screen finishes all result in a crash.
added note:
$ retrofe --version
RetroFE version 0.7.20b1
14
Announcements / Re: New features
« on: January 06, 2017, 08:50:16 PM »
BTW No errors on wired Dual Shock 4 retrofe exit.
Haven't tested bluetooth wireless or Dual Shock 3 yet but I feel it's good.
Haven't tested bluetooth wireless or Dual Shock 3 yet but I feel it's good.
15
Announcements / Re: New features
« on: January 06, 2017, 08:40:46 PM »
I just gave it a whirl on Mac...
I loaded the Sega game. After I quit with esc. The game fires right back up without me selecting it. I quit again. The game starts back up in a loop. It's as though all the key presses from hitting spacebar the 1st time are still firing.
Nothing in the logs.
I loaded the Sega game. After I quit with esc. The game fires right back up without me selecting it. I quit again. The game starts back up in a loop. It's as though all the key presses from hitting spacebar the 1st time are still firing.
Nothing in the logs.