When a %bv control is used, pressing a letter key jumps you to a branch starting with that letter, say for example you have 2 items 'Michael' and 'Mary' (with Michael first), then pressing M jumps to 'Michael' and the second press goes to 'Mary', the third press back to 'Michael' and so forth. This strikes me as intentional, not random. Closed-up branches aren't included - until they are opened (which the space bar does) ... and then they are. This is an implicit type of accelerator key behaviour that I couldn't see documented anywhere.
All well and good until one uses the cursor keys, whereupon we jump between entries with no discernable pattern, (including highlighting buttons) eventually ending up with an Access Violation error.
After the mouse, cursor keys are the next most intuitive way to go up and down a %bv list, so this interesting behaviour has to be handled. Presumably the correct method is to call ADD_KEYBOARD_MONITOR@ abd deal with the key presses as they occur. Can the ADD_KEYBOARD_MONITOR@ callback simply throw the keypresses away as they are caught? Since the control clearly does handle keyboard input, what precisely is it doing in response to cursor keys please?
Eddie