From: George H. <geo...@us...> - 2013-11-20 11:48:15
|
Update of /cvsroot/win32forth/win32forth/Help/html In directory sfp-cvs-1.v30.ch3.sourceforge.com:/tmp/cvs-serv19190 Modified Files: class-generic.htm dexh-w32fmsg.htm Log Message: Updated docs Index: dexh-w32fmsg.htm =================================================================== RCS file: /cvsroot/win32forth/win32forth/Help/html/dexh-w32fmsg.htm,v retrieving revision 1.5 retrieving revision 1.6 diff -C2 -d -r1.5 -r1.6 *** dexh-w32fmsg.htm 15 Mar 2013 00:25:01 -0000 1.5 --- dexh-w32fmsg.htm 20 Nov 2013 11:48:12 -0000 1.6 *************** *** 53,57 **** </pre><p>The lines marked (*1*) (*2*) and (*3*) are all you need to set your application's inter-process identification & communication capabilities. ! </p><p>The default action is using none of theese lines, the result in this case is: </p><ul><li>While developping, your program is considered to be win32Forth itself. It is able to communicate with Help and IDE, for example for using the debugger. --- 53,57 ---- </pre><p>The lines marked (*1*) (*2*) and (*3*) are all you need to set your application's inter-process identification & communication capabilities. ! </p><p>The default action is using none of these lines, the result in this case is: </p><ul><li>While developping, your program is considered to be win32Forth itself. It is able to communicate with Help and IDE, for example for using the debugger. *************** *** 105,109 **** WM_COPYDATA, that can send any block of data to another window. </p><p>Each application can create a set of win32forth-specific messages, identified ! by custom messages numbers. Theese message identifiers must be loaded in both applications so that they understand each other. </p><p>The contents of a win32forth --- 105,109 ---- WM_COPYDATA, that can send any block of data to another window. </p><p>Each application can create a set of win32forth-specific messages, identified ! by custom messages numbers. These message identifiers must be loaded in both applications so that they understand each other. </p><p>The contents of a win32forth Index: class-generic.htm =================================================================== RCS file: /cvsroot/win32forth/win32forth/Help/html/class-generic.htm,v retrieving revision 1.6 retrieving revision 1.7 diff -C2 -d -r1.6 -r1.7 *** class-generic.htm 15 Nov 2013 17:40:43 -0000 1.6 --- class-generic.htm 20 Nov 2013 11:48:12 -0000 1.7 *************** *** 11,37 **** <h1>Generic-Window -- Base class for all window objects. </h1><p>Generic-Window is the base class for all window objects. This class ! contains a single ivar, hWnd, that is the (MS Windows) handle for the window. This class encapsulates all the Win32 API calls that specify a window handle. There will be the following subclasses of Generic-Window: </p><ul> ! <li><a href="clas-Window.htm">Window</a> Adds a device context and the ablility to display text and graphics output.</li> ! <li><a href="clas-Dialog.htm">Dialog</a> Support for dialog boxes</li> ! <li><a href="clas-Control.htm">Control</a> Adds support for the standard Win32 controls with subclassing.</li> </ul> <p>Since Generic-Window is a generic class it should not be used to create any instances. <br /> The Global Rectangle objects wRect and WndRect ( originally ! defined in Window.f ) have been replaced by a Rectangle IVAR WinRect so that Windows in different threads don't interfere with each other's drawing operations. <br /> - For backwards compatibility wRect is defined as an int which is set - to the address of WinRect by the ClassInit: method ( and WndRect is defined as - an alias of wRect in Window.f. Also ) however WinRect should be used in new - code since it uses early binding. ClientRect in class EditControl ( in Controls.f ) - is also defined as an alias of wRect for compatibility. <br /> - We also provide wRect as an alias of TempRect for compatibility. <br /> - Temporarily added new generic class Dialog&Control and moved some code into it and - duplicated the same code in Class Window so that Ivar offsets in Class Window are - the same for temporary compatibility. </p><h2>Glossary </h2><p><b><code>: get-mouse-xy ( hWnd -- x y) \ W32F --- 11,29 ---- <h1>Generic-Window -- Base class for all window objects. </h1><p>Generic-Window is the base class for all window objects. This class ! contains an ivar, hWnd, that is the (MS Windows) handle for the window. This class encapsulates all the Win32 API calls that specify a window handle. There will be the following subclasses of Generic-Window: </p><ul> ! <li><a href="class-Window.htm">Window</a> Adds a device context and the ablility to display text and graphics output.</li> ! <li><a href="class-Dialog.htm">Dialog</a> Support for dialog boxes</li> ! <li><a href="class-Control.htm">Control</a> Adds support for the standard Win32 controls with subclassing.</li> </ul> <p>Since Generic-Window is a generic class it should not be used to create any instances. <br /> The Global Rectangle objects wRect and WndRect ( originally ! defined in Window.f ) are now synonyms of temprect ( defined in class.f ) ! which has been made a User Object so that Windows in different threads don't interfere with each other's drawing operations. <br /> </p><h2>Glossary </h2><p><b><code>: get-mouse-xy ( hWnd -- x y) \ W32F |