exposurses

Seg faults on exit, but haven't fixed that bit yet. check-in: ecdc9d9bca user: base@atomicules.co.uk tags: trunk, temp

- Make it function so that user is constrained to exposure menu
initially and must select value there.
- Once selected, the ISO menu becomes active and user must select value
there
- Finally make both shutter and aperture menus actives (switch between
them with left/right arrow keys). Whichever is selected, the other
will be calculated.

This is not very pretty:

- I don't like having both the selection_counter and menu_counter. Seems
almost redundant. Made sense before I constrained selections and
stepped through the menu's etc (and therefore you could re-select),
but now seems annoying to have to keep it only for how last two menus
work.
- I don't like the repetitive menu creation stuff. That should be DRY-ed
up. check-in: 580afe6ab4 user: base@atomicules.co.uk tags: origin/master, trunk

- Add in free memory bits, also missed some for the other menus check-in: 6c315c3200 user: base@atomicules.co.uk tags: origin/master, trunk

- Add learning notes
- Use scroll page up/down and item up/down to force refresh and stop
two items showing as selected check-in: dd2fc74444 user: base@atomicules.co.uk tags: origin/master, trunk

Also: More evidence I am in a continual half-daze

- Need to define shutter value as double in `aperture` as otherwise both
arguments will be integers and I'm guessing it'd not going to work out
well. Plus... need to use `fraction_to_double` anyway to feed the
value in.
- Had done the "substring" thing wrong in `strncpy` and was one decimal
place off in getting the paerture value. I.e. would have got "1."
instead of "1.4" from "f/1.4"
- Like the fool I am, in the loop and the copy and paste I'd done, I'd
not changed from `aperture_array[0]` to `aperture_array[n]` check-in: 845d8653eb user: base@atomicules.co.uk tags: origin/master, trunk

I mean, just how? I think I need a few years more sleep or something check-in: 506ba48833 user: base@atomicules.co.uk tags: origin/master, trunk

See this commit: 8d3e66b5ecffa8bcf7691c3f0600840b934beb1a

I'm such an idiot.

- Remove `set_top_row` when setting the shutter menu to the correct
value. Leaving this in fooled me into thinking I had things working
because I just happened to test on the matching ISO/Aperture values.
Plonker. And then it turns out, there was loads wrong.
- Need to include stdlib.h for `strtod` function, otherwise it uses some
kind of stub function (no complaints in compile or use, but it just
doesn't work).
- Wasn't passing right kind of values to `shutter` anyway! Need to
convert these to numeric
- Need to use `fabs` not `abs` for doubles.
- In `nearest_match` wasn't using the correct arrays, had copied over
`iso_array` and forgotten to change them
- Use `strstr` instead `strchr` as couldn't get the former to work and
was probably the wrong one to be using
- Leave some commented out stuff at the bottom that I've been using for
debugging
- check-in: 68919dca22 user: base@atomicules.co.uk tags: origin/master, trunk

Since it doesn't matter if it's longer.
And I'm only using short strings. check-in: 99eba10b76 user: base@atomicules.co.uk tags: origin/master, trunk

So far only implemented on Shutter menu, i.e. have to select ISO and
Aperture, it will then use the equations to calculate the exact required
shutter speed, but then select the nearest value in the menu.

In order to do that added these two functions:

- nearest_match
- fraction_to_double

The latter needed, because need to convert "1/1000", etc into float. For
Aperture menu items can just strip off the "f/".

Seems to work for Sunny 16. check-in: 6513b427e7 user: base@atomicules.co.uk tags: origin/master, trunk

Track the selected values, but for now still do the dummy row shift
thing. check-in: 10d5131043 user: base@atomicules.co.uk tags: origin/master, trunk

not at all DRY though at the moment. check-in: 0ecf3fd90c user: base@atomicules.co.uk tags: origin/master, trunk

Requires the Window and Menu variables to be global(?) in scope. I.e.
move outside of main routine.

Interesting thing about the refreshing of the other menu... check-in: 328662366f user: atomicules@lavabit.com tags: origin/master, trunk

Still need a way to get to the third menu and also need to actually do
something with the User Pointer function.

Baby steps though. check-in: b4468458f4 user: atomicules@lavabit.com tags: origin/master, trunk

Was meant to be like this in the first place check-in: b5ca845268 user: atomicules@lavabit.com tags: origin/master, trunk

At least I don't think these are needed? check-in: e4e256f8b0 user: atomicules@lavabit.com tags: origin/master, trunk

Or whatever the hell they are called. Inadvertently set these wrong when
adding in the third menu. check-in: 18f4d20e48 user: atomicules@lavabit.com tags: origin/master, trunk

Probably overkill for such a tiny file, but good practice for me. check-in: fc1d33f903 user: atomicules@lavabit.com tags: origin/master, trunk

- Oh my, I've ended up using pointers to pointers already! Use this so
can switch the menu/win "pointing" at with left and right keys and
then scroll up down the active one.
- Also means need to just use plain getch and not wgetch as don't want
to limit input to one window.

I still don't get what determines an active window. Is it just cursor
position? check-in: db667542ca user: atomicules@lavabit.com tags: origin/master, trunk

Tricky bit was that have to re-create my_items. I thought I'd be able to
re-use that for the sake of this test. But without recreating it the
second menu is blank. check-in: 8fab8d5ebf user: atomicules@lavabit.com tags: origin/master, trunk

Example from here:
http://tldp.org/HOWTO/NCURSES-Programming-HOWTO/intro.html check-in: 97c4a398a9 user: atomicules@lavabit.com tags: origin/master, trunk