Return to readme.txt CVS log

Up to [WindowsNT SDKs] / mstools / samples / spincube

Annotation of mstools/samples/spincube/readme.txt, revision 1.1

1.1     ! root        1:  Sample: Standard DLL & example of Creating a Custom Control Class
        !             2: 
        !             3: Summary:
        !             4: 
        !             5: The SPINCUBE sample provides a generic Windows NT dynamic
        !             6: link library template, demonstrating the use of DLL entry
        !             7: points, exported variables, using C runtime in a DLL, etc...
        !             8: 
        !             9: This sample also provides a functional example of how
        !            10: to create a custom control class that may be used by
        !            11: applications (i.e. SPINTEST.EXE) as well the Dialog Editor.
        !            12: 
        !            13: 
        !            14: More Information:
        !            15: 
        !            16: SPINCUBE.DLL contains the control window procedure and the
        !            17: interface functions required by the Dialog Editor (see
        !            18: SPINCUBE.C), as well as the control paint routines (see
        !            19: PAINT.C). SPINTEST.EXE is a small test program that loads
        !            20: SPINCUBE.DLL and creates a few of the custom controls.
        !            21: 
        !            22: To test SPINCUBE with the Dialog Editor:
        !            23: 
        !            24: 1.Start the editor. From the File menu, choose Open Custom.
        !            25: 
        !            26: 2.Enter the path and filename of SPINCUBE.DLL.
        !            27: 
        !            28: 3.Create a new dialog box and choose a custom control
        !            29:   button from the control palette (lower-right corner).
        !            30: 
        !            31: 4.Click the dialog box to create a SPINCUBE control.
        !            32: 
        !            33: 5.Save the dialog box template.
        !            34: 
        !            35: 6.Inspect the .DLG file that was created.

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.