Wow - what can I say? Thanks for all your engagement. It makes me happy to see that it isn't that simple to be blamed for the thread. But I'm still confused of all that stuff - because I do not understand half of it. I know where I'm wrong, but I'm not sure about the solution. Probably my solution could also be something complete different. Will all your Input I can proove my requirements and find the proper way.
What I have to do:
Define in a config-file some Curves to be used for calculation later. It should be separate that a "user" can find all parameter at one place. Something like this:
int curve[10][11] = {
{0,25,35,40,45,50,55,60,65,75,100}, // Curve 0 with 11 points (for each)
{0,10,20,30,40,50,60,70,80,90,100}, // Curve 1
{0,10,20,30,40,50,60,70,80,90,100}, // Curve 2
{0,10,20,30,40,50,60,70,80,90,100}, // Curve 3
{0,10,20,30,40,50,60,70,80,90,100}, // Curve 4
{0,10,20,30,40,50,60,70,80,90,100}, // Curve 5
{0,10,20,30,40,50,60,70,80,90,100}, // Curve 6
{0,10,20,30,40,50,60,70,80,90,100}, // Curve 7
{0,10,20,30,40,50,60,70,80,90,100}, // Curve 8
{0,10,20,30,40,50,60,70,80,90,100} // Curve 10
};
In the Setup, I definie for what calculation I use what "Curve" (the values represents percentages). The defined Curve should be stored in the Object for later use. Thats why I defined the setExpo()-Function. I will have several Instances of that object, and every instance should manage the own curve which can be one of the defined above. I then have a function calle applyExpo(). This function multiply another value read from analog with one in the curve (well, there is some more math to decide which of the 11 values, but for understanding it is that easy).
So then, I don't relly need sizeof, because the range (row and cols) are fix. But that is not the only problem I have - right?
The question is: Do I have to store the curve within the object-instance? For me, I sayed yes. But probably there are other common ways.
Later, I like to have a config-file on a SD-Card - this here is just a walk around until I have the module. Makes this easier? Sould I only tell the object which curve to use and read the values at run time instead of sending as parameter?
To the case:
I use a teensy 3.1. There are some gimbals (poti) connected. Based on the position, I have to create a ppm-stream to control a servo in a RC-plane. All used potis in the gimbals are linear. But for flight, the most "pilot" prefer to have a wider range in the middle. Most RC Transmiters use an exponential-function for that. I prefer to have a curve, where the character can be more expressed...