On 1 Nov 2003 08:30:44 -0800,
te********@hotmail.com (Edward) wrote:
<snip>
Thanks for this. The form is by now far too complex to be reworked in
the way that you suggest.
In that case it is about time you ripped the App apart and rebuilt it
However, within the terms of reference of
my application, you are wrong when you suggest that "If you want to
allow none or all, you should use check boxes".
Actually, I think he is right
- your problem is the peculiar behaviour of 'grouped' option buttons
- check boxes do not behave in that perverse manner
- however personally I would use a UserControl ...
My application is
designed to capture survey data, and no entry is marked down as no
answer. Although I suppose I could add an extra option button for
just that contingency, though we are seriously running out of screen
real estate.
The 'no answer' bit is not relevant to your problem
- and I don't think Raoul was suggesting that it would help
- that is just an explanation of the perverse behaviour of grouped
option buttons (and frankly I don't think it is quite correct - it is
actually down to the Arrow keys - and sadly windows nicks them before
the KeyDown event )
If you are running out of 'screen real estate' then you need to have a
major re-think
Also, if you want to add a question, and you have to touch the source
code, you are skating on thin ice.
Your Form should contain just one Control Array of the very
peculiar/specific input types that you have created
- ideally driven from a parameter file
Look into UserControls, and have a look at some of the more
interesting Windows APIs - DrawFrameControl comes to mind