runcommand - launch image - wait until button press

[CargoRunner]

The runcommand settings "launch menu art" and "Launch Image Delay" allow you to display an image before the game loads (rather than while the game loads as far as I understand).

I am using these images to display some of the game artwork and also provide some instructions on how to play the game [a jpg file in the configuration directory with a "-image" tag in the filename]. Sometimes you play the same game a lot so you don't need instructions any more. Sometimes you play a game rarely and you need to check what button does what in the game. So you need a different delay time in those two cases.

I understand that this part of the launching process is the opportunity for the user to press a button and configure the launching of the game.

Would it be possible to have a special "Launch Image Delay" (for example -1 or 999) that would wait for the user to press a button (a different button to the button that jumps to the lunching configuration screen). With this special setting the user can press nothing and take as long as they wish to read the game instructions/help. Or the user can just press the new button to skip straight to loading the game if they do not need any help and don't need to change any settings.

I tried to modify the runcommand script myself but I don't have any unix skills and I didn't know if I am "running under X" or not, so it didn't work. I think this is the part of the code that does the delay.

if [[ -n "$image" ]]; then
# if we are running under X use feh otherwise try and use fbi
if [[ -n "$DISPLAY" ]]; then
feh -F -N -Z -Y -q "$image" & &>/dev/null
IMG_PID=$!
sleep "$IMAGE_DELAY"
else
fbi -1 -t "$IMAGE_DELAY" -noverbose -a "$image" </dev/tty &>/dev/null
fi
elif [[ "$DISABLE_MENU" -ne 1 && "$USE_ART" -ne 1 ]]; then
local launch_name
if [[ -n "$ROM_BN" ]]; then
launch_name="$ROM_BN ($EMULATOR)"
else
launch_name="$EMULATOR"
fi
DIALOGRC="$CONFIGDIR/all/runcommand-launch-dialog.cfg" dialog --infobox "\nLaunching $launch_name ...\n\nPress a button to configure\n\nErrors are logged to $LOG" 9 60
fi
}

[BuZz]

@CargoRunner please use markdown to format the code.

[Clyde]

Feh lets you configure its actions for keyboard keys and mouse buttons. See its manpage for further information, and this post in the official Raspberry Pi forum. The action to exit feh is called quit in its configuration files.

So, maybe you could configure a quit key in feh and set a very high delay time in Retropie. Just an idea after a little research, I don't have any practical experience with this.