#15264: No Multicell line for wxGrid in Combination with wxPanel or wxNotebook

[wxTrac]

Ticket URL: <http://trac.wxwidgets.org/ticket/15264>

#15264: No Multicell line for wxGrid in Combination with wxPanel or wxNotebook
--------------------+-------------------------------------------------------
Reporter: HelgeB | Owner:
Type: defect | Status: new
Priority: normal | Milestone:
Component: wxGrid | Version: 2.9.1
Keywords: | Blockedby:
Patch: 0 | Blocking:
--------------------+-------------------------------------------------------
When I use wxGrid with AutoWrapCellEditor as a control item in a wxPanel
or wxNotebook (wxAuiNotebook maybe also) I can not use multicell line. The
same error occurs when I use wxGrid with RichtextCtrl or wxAdvTable with
wxTextCtrl or wxRichtTextCtrl.


When I put wxGrid directly in the MainFrame (wxFrame) then I can create
the next line with Ctrl-Enter. The wxGrid shows the multi lines correctly.
When I put wxGrid in a wxPanel (or wxNotebook or other container) and I
use Ctrl-Enter then the cursor is moved to next row of the grid. Also
other enter combination jumps always to the next cell in the next row.
Therefore I can not use multi line cell which is very important.

I debug the process and the combination with wxFrame the wxTextCtrl or
wxRichTrxtCtrl get the event Ctrl-Enter command.
If wxPanel/wxNotebook as parent window the command event is captured and
the text control doesn't get the event.
A wxText (multiline) has the same problem, the event doesn't hand over to
the control.
Some additional windows styles When I use wxGrid with AutoWrapCellEditor
as a control item in a wxPanel or wxNotebook (wxAuiNotebook maybe also) I
can not use multicell line. The same error occurs when I use wxGrid with
RichtextCtrl or wxAdvTable with wxTextCtrl or wxRichtTextCtrl.


When I put wxGrid directly in the MainFrame (wxFrame) then I can create
the next line with Ctrl-Enter. The wxGrid shows the multi lines correctly.
When I put wxGrid in a wxPanel (or wxNotebook or other container) and I
use Ctrl-Enter then the cursor is moved to next row of the grid. Also
other enter combination jumps always to the next cell in the next row.
Therefore I can not use multi line cell which is very important.

I debug the process and the combination with wxFrame the wxTextCtrl or
wxRichTrxtCtrl get the event Ctrl-Enter command.
If wxPanel/wxNotebook as parent window the command event is captured and
the text control doesn't get the event.
A wxText (multiline) has the same problem, the event doesn't hand over to
the control.

I create a wxGrid or wx(Rich)TextCtrl in the MainFrame (wxFrame) configure
the styles and so on. The multiline is working. Now move the control to a
wxPanel/wxNotebook in the MainFrame. The multi cell line doesn't work
anymore.

The same problem is in the 2.9.3 also.
I use Dialogblocks (5.0.3, before 4.5?) to create the structure with
visual express studio 2008 compiler and debugging.
Configuration is Unicode Debug wxMSW and Debug wxMSW.


Own capture of the event (e.g. with wxTE_PROCESS_ENTER or
wxTE_PROCESS_TAB) doesn't work also. The event will be captured alwys.
multiline and wxRichTextCtrl is needed for next program version.

I should configured correctly the controls.


see also
http://forums.wxwidgets.org/viewtopic.php?f=1&t=37320&p=151825&hilit=helge#p151825

Reproducable: yes, always

see also
http://forums.wxwidgets.org/viewtopic.php?f=1&t=37320&p=151825&hilit=helge#p151825

Reproducable: yes, always


--
Ticket URL: <http://trac.wxwidgets.org/ticket/15264>

[wxTrac]

Ticket URL: <http://trac.wxwidgets.org/ticket/15264#comment:1>

#15264: Ctrl+Enter can't be used for wxGrid cell editing when parent is a wxPanel

--------------------+-------------------------------------------------------
Reporter: HelgeB | Owner:
Type: defect | Status: new
Priority: normal | Milestone:
Component: wxGrid | Version: 2.9.1
Keywords: | Blockedby:
Patch: 0 | Blocking:
--------------------+-------------------------------------------------------

Comment(by vadz):

As always, it would be very useful to have an as small as possible
[HowToSubmitPatches patch] to the grid sample allowing to reproduce the
problem. Could you please make one?


--
Ticket URL: <http://trac.wxwidgets.org/ticket/15264#comment:1>

[wxTrac]

Ticket URL: <http://trac.wxwidgets.org/ticket/15264#comment:2>

#15264: Ctrl+Enter can't be used for wxGrid cell editing when parent is a wxPanel

--------------------+-------------------------------------------------------
Reporter: HelgeB | Owner:
Type: defect | Status: new
Priority: normal | Milestone:
Component: wxGrid | Version: 2.9.1
Keywords: | Blockedby:
Patch: 0 | Blocking:
--------------------+-------------------------------------------------------

Comment(by HelgeB):

I attached files for short check.
This code doesn't contain additional event handler to capture the Ctrl-
Enter. I tried this and tried some exapmples (workarounds from internet)
which are not implemented. The events and workaround doesn' work. Sadly I
put all different samples and tries into the trash.

Type a text in the Grid in the second column and second row (B2). Press
ctrl-enter and the text is broken into next line of the cell (working
example).
If you do this in the non working examples (when wxPanel is used) after
ctrl-enter the cursor is jump to the next control (text control).


--
Ticket URL: <http://trac.wxwidgets.org/ticket/15264#comment:2>

[wxTrac]

Ticket URL: <http://trac.wxwidgets.org/ticket/15264#comment:3>

#15264: Ctrl+Enter can't be used for wxGrid cell editing when parent is a wxPanel

--------------------+-------------------------------------------------------
Reporter: HelgeB | Owner:
Type: defect | Status: new
Priority: normal | Milestone:
Component: wxGrid | Version: 2.9.1
Keywords: | Blockedby:
Patch: 0 | Blocking:
--------------------+-------------------------------------------------------

Comment(by vadz):

Sorry but could you ''please'' read the HowToSubmitPatches instructions? I
really don't have the time to look at all the code in these ZIPs, it would
be great if you could please add just the few lines that should be enough
to show the problem to the sample instead.


--
Ticket URL: <http://trac.wxwidgets.org/ticket/15264#comment:3>