exposurses

I still hadn't got things quite right from when I'd split out the menu
and window creation functions. The segfault on exit was due to the item
pointers I thought existed not actually existing.

Need to make sure they exist as expected as otherwise I can't free up
the memory, etc.

Yay, pretty much done. file: [c60faa0626] check-in: [d39151ac51] user: base@atomicules.co.uk branch: origin/master, size: 13201

Since this seems easier than trying to prevent selection. file: [b83c1efdbb] check-in: [4cc8e33f3c] user: base@atomicules.co.uk branch: origin/master, size: 12861

Keeping the NULLs in makes array indices very confusing, but this seems
to be the right thing to do. file: [6df7670132] check-in: [7312ab2b6f] user: base@atomicules.co.uk branch: origin/master, size: 12137

Didn't change functionality (it was still working), but just gives
better consistency to the code. file: [a6a32e4841] check-in: [4a3cabadc2] user: base@atomicules.co.uk branch: origin/master, size: 10939

I was still using the "variable pointers" technique, well trying to, and
it wasn't working for things like `set_menu_win` so pull this back out
into main.

Seg faults on exit, but haven't fixed that bit yet. file: [7d4000ba2d] check-in: [c2741c67e7] user: base@atomicules.co.uk branch: origin/master, size: 11195

instead of trying to wrap everything in one. This way I know I can
return the correct thing and I know I'm setting things as expected.

As opposed to previous attempt where I was (trying) to use variable
pointers, but with pointers to pointers, etc. And was obviously a bit
beyond me. file: [1fbc889f09] check-in: [e4268c4b4e] user: base@atomicules.co.uk branch: origin/master, size: 10784

As otherwise can't free up the memory, etc. This makes clean up work

Yay, pretty much done. file: [3641283e71] check-in: [cf92beadf9] user: base@atomicules.co.uk branch: temp, size: 13101

Although this version still no worky file: [95d8229153] check-in: [b786f69eac] user: base@atomicules.co.uk branch: temp2, size: 10468

Seg faults on exit, but haven't fixed that bit yet. file: [1a85fe6722] check-in: [ecdc9d9bca] user: base@atomicules.co.uk branch: temp, size: 11245

- 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. file: [519009a683] check-in: [580afe6ab4] user: base@atomicules.co.uk branch: origin/master, size: 12716

- Add in free memory bits, also missed some for the other menus file: [ae4e3659ee] check-in: [6c315c3200] user: base@atomicules.co.uk branch: origin/master, size: 12677

- Add learning notes
- Use scroll page up/down and item up/down to force refresh and stop
two items showing as selected file: [82aebcb54e] check-in: [dd2fc74444] user: base@atomicules.co.uk branch: origin/master, size: 11196

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]` file: [77daf0d603] check-in: [845d8653eb] user: base@atomicules.co.uk branch: origin/master, size: 10796

I mean, just how? I think I need a few years more sleep or something file: [1537cc47cc] check-in: [506ba48833] user: base@atomicules.co.uk branch: origin/master, size: 10733

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
- file: [b4271e267b] check-in: [68919dca22] user: base@atomicules.co.uk branch: origin/master, size: 10733

Since it doesn't matter if it's longer.
And I'm only using short strings. file: [bd9849a6f1] check-in: [99eba10b76] user: base@atomicules.co.uk branch: origin/master, size: 10614

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. file: [35b1eab5db] check-in: [6513b427e7] user: base@atomicules.co.uk branch: origin/master, size: 10586

Track the selected values, but for now still do the dummy row shift
thing. file: [3224c31d31] check-in: [10d5131043] user: base@atomicules.co.uk branch: origin/master, size: 8948

not at all DRY though at the moment. file: [09d2291528] check-in: [0ecf3fd90c] user: base@atomicules.co.uk branch: origin/master, size: 8288

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... file: [532e98b06f] check-in: [328662366f] user: atomicules@lavabit.com branch: origin/master, size: 5966

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. file: [2714035e0a] check-in: [b4468458f4] user: atomicules@lavabit.com branch: origin/master, size: 5780

Was meant to be like this in the first place file: [2c21b9d30c] check-in: [b5ca845268] user: atomicules@lavabit.com branch: origin/master, size: 5197

At least I don't think these are needed? file: [51415149f3] check-in: [e4e256f8b0] user: atomicules@lavabit.com branch: origin/master, size: 5193

Or whatever the hell they are called. Inadvertently set these wrong when
adding in the third menu. file: [85ec447a29] check-in: [18f4d20e48] user: atomicules@lavabit.com branch: origin/master, size: 5244

- 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? file: [c404445cec] check-in: [db667542ca] user: atomicules@lavabit.com branch: origin/master, size: 4113

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. file: [70bdf368d7] check-in: [8fab8d5ebf] user: atomicules@lavabit.com branch: origin/master, size: 4020