Yes, in my code the parent of the edit control is the list control.
ID set to 1.
capability of list controls
"Mikel" <mikel.l...@gmail.com> wrote in message
news:27a951a4-f101-4843-8aef-57ede81abefe@8g2000hse.googlegroups.com...
On 13 mayo, 16:13, Joseph M. Newcomer <newco...@flounder.com> wrote:
As already observed, 1 is an exceptionally bad choice here. I tend to
create controls
like this when I need to do this in the range of 10000-30000.
joe
On Tue, 13 May 2008 03:56:31 -0700 (PDT), Mikel <mikel.l...@gmail.com>
wrote:
Hi all:
I'm creating an edit control on the fly, to implement in-place editing
on a CListCtrl, and I was wondering wether I need to define an ID for
it in resource.h or I can use whatever value I choose safely.
The CEdit::Create reference has this example, where they use '1' as
the ID:
void CMyView::OnInitialUpdate()
{
CView::OnInitialUpdate();
// dynamically create an edit control on the view
CEdit* pEdit = new CEdit;
pEdit->Create(ES_MULTILINE | WS_CHILD | WS_VISIBLE | WS_TABSTOP |
WS_BORDER,
CRect(10, 10, 100, 100), this, 1);
}
I don't usually create controls on the fly so I'm not quite sure if
this is safe or it's just looking for trouble. My first thought is
that it's not really safe, but I'd like to know it for sure.
Any ideas?
Thanks in advance for your help
Mikel
Joseph M. Newcomer [MVP]
email: newco...@flounder.com
Web:http://www.flounder.com
MVP Tips:http://www.flounder.com/mvp_tips.htm-Ocultar texto de la cita -=
- Mostrar texto de la cita -
Thanks for your answers.
I also felt that 1 was not the best choice, but since that's what they
use in the example for CEdit::Create's documentation, I thought that
maybe it was OK.
Just one thought: why don't they write examples that are correct in
the documentation?