Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!rex!spool.mu.edu!olivea!mintaka!bloom-beacon!eru!hagbard!sunic!mcsun!ukc!tcdcs!wsl!jja
From: jja@wsl.ie (John Allen on wsl)
Newsgroups: comp.windows.ms.programmer
Subject: Re: Read-only Edit Windows
Message-ID: <783@wsl.ie>
Date: 11 Jun 91 22:14:06 GMT
References: <5266@servax0.essex.ac.uk>
Reply-To: jja@wsl.ie (John Allen on wsl)
Organization: Workhorse Systems Limited, Dublin
Lines: 17

In article <5266@servax0.essex.ac.uk> whisd@essex.ac.uk (Whiteside S D B) writes:
>
>I had a query about Read-Only Edit windows.
>
>Many thanks to all who sent me suggestions on how to implement them.
>
>Following up on some of them, I have found one solution to the problem:
>
>i)	Subclass the edit window (using SetWindowLong, GetWindowLong and 
>CallWindowProc to insert your window procedure before the default one)
>

Forgive me if I'm missing something, but
what is wrong with

EnableWnd(hEditWnd, FALSE);    // can't edit
EnableWnd(hEditWnd, TRUE);    // can edit.