Software Support > PowerMAME

PowerMAME - New Derivative Build

<< < (35/45) > >>

MikeQ:

--- Quote from: mahuti on February 16, 2006, 12:42:38 am ---One thing I might mention, re: lighting function of PowerMAME.

While working on the setledwiz app, I thought quite a bit about how to handle the difference between single color LEDs and RGB leds. With the setledwiz app I eventually decided to handle the LED lighting with 2 sets of configs. One CFG deals with which terminal the LED is connected to; i.e.

1 COIN1
3 KEYCODE_X

OK. So that powers on LED 1&3. If you are using an RGB LED it's set up to use
1 COIN1
2 COIN1
3 COIN1
4 KEYCODE_X
5 KEYCODE_X
6 KEYCODE_X

Basically that CFG is the same as LedWiz.cfg is with PowerMAME. Beyond that however, I wanted to control the colors more than just ON/OFF. My solution was to add another CFG file for the colors with intensities corresponding to the LedWiz app. This makes for a nice compromise between automation and custom.

1 48
2 0
3 0
(this would be solid red)
4 48
5 38
6 5
(this would be yellow)
7 35
8 48
9 48
(this would be white)
10 129
11 0
12 0
(this would be pulsing red)

This would be a nice feature to continue to have in PowerMAME. The SetLedWiz currently has this, but it's much nicer to pursue the all-in-one solution. I haven't had time to look at the source yet of PowerMAME. I'll look tomorrow and see what's goin on.

--- End quote ---

I need to get a better grasp of what people want to do with the RGB lighting.  If people want every game to have the ability to light any control, any color, this will get complicated.

If people want certain controls to always be the same color, this will be easy.

Can people comment on how they intend to use the RGB stuff?  My panel is monochromatic so I haven't put much thought into the RGB stuff.

Tiger-Heli:

--- Quote from: MikeQ on February 16, 2006, 10:32:40 am ---I need to get a better grasp of what people want to do with the RGB lighting.  If people want every game to have the ability to light any control, any color, this will get complicated.

If people want certain controls to always be the same color, this will be easy.

Can people comment on how they intend to use the RGB stuff?  My panel is monochromatic so I haven't put much thought into the RGB stuff.

--- End quote ---
I don't have a personal opinion, but it's probably best to prepare for the most complicated option.

MikeQ:

--- Quote from: Tiger-Heli on February 16, 2006, 10:52:06 am ---
--- Quote from: MikeQ on February 16, 2006, 10:32:40 am ---I need to get a better grasp of what people want to do with the RGB lighting.  If people want every game to have the ability to light any control, any color, this will get complicated.

If people want certain controls to always be the same color, this will be easy.

Can people comment on how they intend to use the RGB stuff?  My panel is monochromatic so I haven't put much thought into the RGB stuff.

--- End quote ---
I don't have a personal opinion, but it's probably best to prepare for the most complicated option.

--- End quote ---

That is a given.  :D  Things should never be easy.   I'm looking for ideas that I hadn't though of that will complicate things further.

Tiger-Heli:

--- Quote from: MikeQ on February 16, 2006, 10:56:36 am ---I'm looking for ideas that I hadn't though of that will complicate things further.

--- End quote ---
Check your E-mail then.

mahuti:
During my thinking process... this is the decision that I came to.

A good automated coloring scheme picks a users highest priority color and pairs it with the highest priority input. I.e, favorite color one goes with mames input1, favorite color 2 goes with mame's input2. For more complex color requests, there is the option of using romname.lwa files, which I think you already support (am I wrong on that?) From a user interface perspective, that provides some context for the button's functionality. Many games (somewhat) have a primary & secondary, tertiary button priorities, and Mame's cfg is written somewhat like that. Not a major rationalle for this method, but better than a shot in the dark.

For the SetLedWiz, I used the LED cfg to explain where the LEDS were. Then I used the color CFG to set the color priority. Input 1 will always use "red" Input 2 will always use "blue" regardless of the KEYCODE assigned to Input 1.

It gets more complex when you assume that a user will always want KEYCODE_X button to always be a certain color. I haven't provided for that eventuality yet, but I will... basically the option to choose between color priority, and color position, would seem to me to be the basic differences between user color choice for button highlighting. Any deeper scheme would be more on a Case by case basis, a la the LWA files.

To sum up, with RGB lighting, to me there would seem to be the following color cases;
1. Contextual lighting
2. Positional lighting
3. Per Game custom lighting.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version