>  >  - clicking doesn't work well (it often selects one digit rather
>  >    than both.  The spin control then only updates the one digit)
>  
>  This was intentional design; it depends on where you click.  If 
>  you click at the front of the field, the entire thing is selected;
>  if you click after the 1st digit, it selects just that digit.
>  You can also click at the front and then hit shift-left and
>  select just the 1st digit.  I wanted the user to be able to 
>  select one digit at a time and then spin through its logical 
>  values.  I take it this is not desired behavior?

I don't like this behaviour.  It makes sense to someone who is trying
to be very precise, but I think is too finnicky for an average user.

In particular contrast it with the standard Windows time control
that updates the whole field no matter where you have clicked
in it.

>  I agree that it's really annoying.  If I fix this, is the
>  selection issue still a problem?

I don't think you should allow selecting of an individual 
digit.  Just work on whole fields for all keyboard and mouse
stuff.  I suspect very few people intentionally try to work
on a single digit.

The existing Windows control is always a whole field.
 
>  >  - you have to have only the 'A' or 'P' selected to use the
>  >    keyboard for A/P (it does nothing if the 'M' is also selected)
>  
>  Hmmm.  This isn't the case under MSW; you can select either the 
>  whole field or just the A/P and type the opposite to change 
>  the field.  What OS/Python/wxPython are you using?

I was under Win98SE with 2.4.0.6.  Again I think this should work as
a whole field thing.  It should change if any of it is selected.

Roger

---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-users-unsubscribe@[...].org
For additional commands, e-mail: wxPython-users-help@lists.wxwindows.org