@mitu

Thank you mitu, I appreciate your reply, will go have a look into that.

@kkokkinos There are a few GPIO based controller drivers available in RetroPie:

I think you're trying to use the mk_arcade_joystick_rpi one ? If so, then you need to install it first from the RetroPie-Setup script (it's in the drivers section of the packages) and then configure it - as described on the Github page of the driver. You can ignore all the installation steps and just look at the pinout and make sure you connected the wires correctly, then jump to the Loading the driver section.

There is no recalbox.conf file in RetroPie, that is part of the Recalbox image -a different project.

TO THE RETROCAVE!!!

alt text

@herb_fargus Users who wish to contribute but have no coding experience could help with this.

@herb_fargus said in Retropie Youtube channel ??:

I got tired of enabling people to rip off the project with stupid proof tutorials

I dont know how to tackle this but we can try.

For all those thinking that every option will have help it is not so. The help message will only be shown in Option List / Multiselect Lists atleast at present. Also Help text is optional ie. it is shown only if defined for an option. This allows help to be shown only for complex/ambiguous options like Audio Device selection (both, the one with PCM and the one with Alsa). Many users dont know what these options do and adding a small help text solves this problem.

@pjft Is Random Screensaver in help necessary?

@TMNTturtlguy Your suggestion is also acceptable.

What I was mostly going for was when a user doesnt know what an option does, they might be inclined to checkout all options in < > Type of setting (OptionList). Clicking A on that opens a list of text components. Here we can have some help shown. So help is not obstructing during the normal usage but only shown in deeper menus

I could just use a controller for that with a slideing screen I guess...

@jdrassa
As part of the theming-refactoring, I have started to split out the carousel into it's own GuiComponent-based class.

This gets complicated real quickly, as the carousel should also take care of member population, input handling (incl the texture loading/unloading), so I had dropped it again for now. Things move slow enough as it is X-).

But anyway, if you want me to send you the stubs, let me know.

Btw: if I read the OP correctly, this also is a CR for an 'automatic' carousel, in the sense that it will move through the contained members on a time interval?

@Zigurana
Thank you for the clarification.
I feel like that is the better and more flexible option for themeing.

@Zigurana Well I was really thinking about the pi zero not necessarily the pi 3. Don't the USB controllers need to be encoded to whatever the console needs I figured since retropie was already emulating the console controls it might be easier to figure out a way to output that onto however many data pins they have in say a Dreamcast controller as opposed to designing your own custom program through arduino. I mean your going to have to emulate the controller by the console anyway. Does someone already have a project started for Arduino?

@BuZz

Yep, simple markup is definitely needed for this, at least several different menu item types: regular (button), input, checkbox and maybe numeric slider. This should be enough to stay within the EmulationStation. Onscreen keyboard is needed anyway, even without this nice feature.

Of course fork is a good way to implement this, but I like RetroPie and I want it be better for everyone. So I shared this idea and wanted to hear you opinion first.