Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail
From: "Mayayana" <mayayana@invalid.nospam>
Newsgroups: comp.lang.basic.visual.misc
Subject: Re: RichEdit control question
Date: Sun, 16 Oct 2011 12:02:18 -0400
Organization: A noiseless patient Spider
Lines: 49
Message-ID: <j7eutt$c4s$1@dont-email.me>
References: <j6vomu$ugh$1@dont-email.me> <j781an$4t9$1@speranza.aioe.org> <j7c6m8$8fo$1@dont-email.me> <vnfj97h4j946qd1mbkhvfmm6s6f9vqr2df@4ax.com> <j7cno4$mac$1@dont-email.me> <j7d65b$ff7$1@dont-email.me> <01cc8bb4$370dd7d0$6d01a8c0@k8s8x>
Injection-Date: Sun, 16 Oct 2011 15:57:50 +0000 (UTC)
Injection-Info: mx04.eternal-september.org; posting-host="hA0LZgtsTmFlvERssm/+Tg"; logging-data="12444"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/PCjaKKBFK1ExTPou1W8FoUPEZ/ydpu6s="
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5512
X-Newsreader: Microsoft Outlook Express 6.00.2900.5512
Cancel-Lock: sha1:cCQNAiXtr2kEHzebexRXAKRi9to=
X-Priority: 3
X-MSMail-Priority: Normal
Xref: x330-a1.tempe.blueboxinc.net comp.lang.basic.visual.misc:500

| >    That makes it confusing. There's no such thing
| > as a RichEdit control in the API. A control is a wrapper
| > around the API or other functionality. There's a
| > RichEdit library. (Which comes in several versions,
| > but that's probably not relevant here.) In other words,
| > if you use the API there's no control. There's API. :)
|
| That's not correct. Since Windows 95 the Rich Edit Control is shipped with
| Windows as part of the Windows API, like the "Edit", "Button", etc.
| control. Cmp.
|

"To create a rich edit control, call the CreateWindowEx function, specifying 
the rich edit window class."

http://msdn.microsoft.com/en-us/library/windows/desktop/bb787877%28v=vs.85%29.aspx

At your link the first sentence says this:

"The original specification for rich edit controls is Microsoft Rich Edit 
1.0;"

   A control is a wrapper. As quoted above, the API
provides a RichEdit *window*. One can
create a control using that window. Which is what I said to
the OP. The window itself has no COM properties or methods,
only API messages. Which you know....

   I'm just trying to clear up any confusion in the
discussion, in case the OP thinks he can use some kind
of "Windows RichEdit control" separate from a RichTextBox,
and then only need to use the API for his one specific need.
It wasn't clear to me that he understood that he'd need to
build his control if he starts with a RichEdit window.

  Why are you always splitting hairs lately?


| 
<http://msdn.microsoft.com/en-us/library/windows/desktop/bb787873%28v=vs.85%
| 29.aspx>
| (... Windows Controls > Control Library > Rich Edit > Rich Edit Control
| Overviews > About Rich Edit Controls)
|