RE: [lmi] Deleting contents of wxSpinCtrl's edit subcontrol

[Boutin, Wendy]

Boutin, Wendy wrote:
> Vadim Zeitlin wrote:
> > On Tue, 20 Jun 2006 14:19:24 +0000 Greg Chicares 
> > <address@hidden> wrote:
> > 
> > GC> Vadim--It appears that deleting the contents of a spin control's
> > GC> edit subcontrol has the effect of setting the value to 
> > the minimum,
> > GC> which seems okay (and seems to be the default msw behavior for
> > GC> UPDOWN_CLASS), but is there a way to force the edit 
> subcontrol to
> > GC> repaint that value when the spin control loses focus?
> > 
> >  It seems already to behave like this here. At least this is 
> > the behaviour
> > I see in the controls sample: if you go to "wxGauge" page and 
> > enter any
> > values in the spin control there (it's the second from the 
> > left, the first
> > one is just a text control + spin button) and then press 
> > "Delete" key and
> > either "TAB" away or click on another control, the value 
> > "10", which is the
> > minimum accepted by this control, appears.
> > 
> >  Is this different from what you'd like or do your spin 
> > controls behave differently from the one in the controls sample? 
> > If it's the latter, how can I reproduce this?
> 
> The controls sample behaves almost exactly as we'd like and
> that's different from what we observe in lmi. The closest
> reproducible case I can show in the sample is this:
>   highlight '15' in the spin control you mention
>   press the delete key
>   use the mouse to press either spin button next to the 
>    text control that lives to the left of the spin control
> I observe the spin control doesn't populate '10', but I don't 
> think it ever actually loses focus either because the blinking
> vertical bar is still present there. Maybe that's a different
> issue you're interested in. Tabbing away or clicking any other 
> control causes the minimum value (10) to reappear and that's 
> the behavior we want in lmi. 
> 
> I discovered adding this tag
>   <min>10</min>
> to the control in our xrc file produces the behavior we'd expect
> in lmi. Although I'm not so sure we can actually do that in our
> current implementation because each skin is used for several 
> different products that likely have very different parameters.

Just for completeness, I proved my suspicion by building the 
xrc sample and deleting:
  <max>100</max>
from 'controls.xrc'. That demonstrates the behavior we observe in
lmi.

---------------------------------------------------------
This e-mail transmission may contain information that is proprietary, 
privileged and/or confidential and is intended exclusively for the person(s) to 
whom it is addressed. Any use, copying, retention or disclosure by any person 
other than the intended recipient or the intended recipient's designees is 
strictly prohibited. If you are not the intended recipient or their designee, 
please notify the sender immediately by return e-mail and delete all copies. 

---------------------------------------------------------