help with controls on a theme

[mxstar1]

I flipped the wheel on a theme to horizontal, and i am wondering how to get the wheel to scroll left and right ONLY for this theme, using left and right, not up and down. I dont want to change the controls for the rest of the system, only on this theme. Right now it scrolls left and right, but only by using up and down on my controller. If i swap my controls, then my other vertical wheels go up and down with left and right. Any ideas? Adding custom controls to the layout? I have no idea how to do this

[keilmillerjr]

Bump on a really old topic, but I was wondering the same. Sharing horizontal and vertical navigation on the same machine would require “swapping” controls to not confuse the user. Unless I’m missing something, which I have been lately with all the new features rolling out, only way to accomplish this is to have themes utilize custom keys, or not for default mapping.

[jedione]

this is what i use in my own themes, and just alter as needed

right know the code is set up to do what you need..

Code: [Select]



local flx = fe.layout.width;
local fly = fe.layout.height;
local flw = fe.layout.width;
local flh = fe.layout.height;



function on_signal( sig )
{
switch ( sig )
{
case "up":
fe.signal( "" );

return true;


case "down":
fe.signal( "" );

return true;


case "left":
fe.signal( "next_game" );

return true;


case "right":
fe.signal( "prev_game" );

return true;


case "select":
default:

}

return false;
}

fe.add_signal_handler(this, "on_signal");


though i know you will not like doing it this way,   

[zpaolo11x]

this is what i use in my own themes, and just alter as needed

I do something similar but instead of signaling "next game" and "prev game" I just use fe.list.index++ or fe.list.index--. Why? I honestly don't remember, something to do with how transitions are managed when signaling instead of pressing keys.

[keilmillerjr]

@jedione makes sense. Thank you. Do you have any issues with navigating the config menu trigging your theme?

@zapaolo11x interesting. Do you have a layout of yours I can reference to understand why? I would have thought the other way around. List index can change, but it’s easy for lots of things to hook into a signal change and execute code with it.

[zpaolo11x]

@zapaolo11x interesting. Do you have a layout of yours I can reference to understand why? I would have thought the other way around. List index can change, but it’s easy for lots of things to hook into a signal change and execute code with it.

My Arcadeflow theme uses this method, the layout is huge with a lot of stuff happening, I can craft a minimal version if you think it's useful. If I remember well, I didn't use "next game" "prev game" because I didn't like the transitions it triggered, therefore I'm using index++ with a custom method to take care of long keypresses.