Re: [lmi] [PATCH 1/2] Make InputSequenceEntry friendly to embedding in wxDVC.

[Greg Chicares]

On 2011-08-08 17:33Z, Václav Slavík wrote:
> Hi,
> 
> On 7 Aug 2011, at 23:05, Greg Chicares wrote:
>>  On "Payments" tab, paste this into "Individual payment":
>>    40000 2;99999;100000;100001;110000;120000;130000;140000;150000;0
>>  Click "..." [the "40000" field is highlighted]
>>  Press Enter [the "40000" is overwritten
          ^^^^^ oops--I meant spacebar
but you figured that out...

> I don't see that when I press Enter, it behaves as I would expect: the dialog
> is closed immediately with no change to the data (with wx trunk).
> 
> What I do see, however, is that the Individual payment text entry in the
> background is updated as you type and so the problem is visible even here:
> neither OK nor Cancel have any effect, as the data are updated immediately.

Yes, that's exactly what I meant to say.

> The fix is simple, just don't apply this patch.

Okay.

> But I am truly baffled by this: TransferDataFromWindow() is apparently
> called after every change, but this isn't making any sense. It's what
> you'd want to happen on OS X or GTK+, where OK/Cancel buttons aren't
> used and every change is reflected immediately, but it's certainly
> surprising in the presence of the OK and, especially, Cancel buttons.
> 
> Vadim, do you have any idea what's going on here? I'm not not very
> familiar with this transfer mechanism (as is probably obvious, seeing
> as I didn't even think of using it initially)...

I'd really like to hear the answer, too--AFAICT, TransferDataFromWindow()
shouldn't be called by wx (or at least by wxmsw) unless an Apply button
is pressed or AcceptAndClose() is called.