[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [lmi] Improved input-sequence editor
From: |
Greg Chicares |
Subject: |
Re: [lmi] Improved input-sequence editor |
Date: |
Sat, 28 May 2016 15:23:51 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.8.0 |
On 2016-05-13 00:35, Greg Chicares wrote:
[...]
> (1) When I pop up the tabbed input dialog (instead of editing in
> the wxDataView census manager directly) and focus an input-sequence
> control (without opening the input-sequence editor), the "OK"
> pushbutton is highlighted, and I expect that (as previously)
> pressing Enter will push "OK". But it does nothing. Instead, I think
> Enter really should press "OK".
To see the desired behavior again, modify 'input_sequence_entry.cpp':
comment out wxTE_PROCESS_ENTER
comment out the Connect(wxEVT_TEXT_ENTER...) call
Of course, that's not ideal because it fixes the regression in the
tabbed input dialog at the cost of removing the new behavior in the
census manager.
I naively thought that calling Skip() in InputSequenceEntry::UponEnter()
might solve the problem, but that's the first thing it does (and I'm
pressing plain Enter, not alt-Enter):
if(!wxGetKeyState(WXK_ALT))
{
event.Skip();
return;
}
so I guess wxTE_PROCESS_ENTER changes something that Skip() can't undo.
- [lmi] Improved input-sequence editor, Greg Chicares, 2016/05/12
- Re: [lmi] Improved input-sequence editor, Greg Chicares, 2016/05/12
- Re: [lmi] Improved input-sequence editor, Greg Chicares, 2016/05/27
- Re: [lmi] Improved input-sequence editor, Vadim Zeitlin, 2016/05/28
- [lmi] 72 chars for git log messages [Was: Improved input-sequence editor], Greg Chicares, 2016/05/29
- Re: [lmi] 72 chars for git log messages [Was: Improved input-sequence editor], Greg Chicares, 2016/05/29
- Re: [lmi] 72 chars for git log messages [Was: Improved input-sequence editor], Vadim Zeitlin, 2016/05/29
- Re: [lmi] 72 chars for git log messages [Was: Improved input-sequence editor], Greg Chicares, 2016/05/30
- Re: [lmi] 72 chars for git log messages, Vadim Zeitlin, 2016/05/30
- Re: [lmi] 72 chars for git log messages, Greg Chicares, 2016/05/31
Re: [lmi] Improved input-sequence editor,
Greg Chicares <=