Re: riched20a with ES_READONLY - can still change formatting ?

JJ,

> Though from my tests in Win2000, WinXP, and Win7, the results
> are a bit different than yours. Only the line spacing shortcuts
> (CTRL+1, CTRL+2, CTRL+5), and Cycle Bullet Style shortcuts
> (CTRL+SHIFT+L) still able to change content in read-only mode.
> All other shortcuts (CTRL+L, CTRL+E, CTRL+R, CTRL+=, CTRL+SHIFT+=,
> CTRL+SHIFT+A, etc.) are not able to change content in read-only mode.

I'm running XPsp3, and for me CTRL-R, CTRL-L, CTRL-E and CTRL-R certainly do
work in read-only mode.

I just tested, I read-only mode, CTRL-+ (superscript), and it was indeed
blocked.  Hmmm...

> That's a RichEdit bug! Mainly because the read-only feature is
> partially functional.

It certainly does seem that the read-only feature is only partly functional
(which feels more wrong than not functional at all). I wonder if thats a
normal bug, or a bug-with-seniority (aka: feature). :-)


Bottom line, its not a case of me not knowing and not being able to find the
setting for disabeling the text-formatting keys, it looks to be a bug.

Bummer.  Now I have to go and subclass that control to catch and filter the
WM_KEYDOWN messages.  :-|

> FYI, RichEdit v2.0 which is used in Win9x/ME/NT4 doesn't
> have any text formatting keyboard shortcuts yet, so it's
> likely a bug in RichEdit v3.0+.

In my resource-definition I'm specifying "RichEdit20A" (text, not a 
constant).  Although, thats using an XPsp3 2008 RICHED20.DLL, which contains 
both the v2.0 and v3.0 versions.

Regards,
Rudy Wieser