From sd008ja@UNIDUI.UNI-DUISBURG.DEWed Jul  5 13:16:52 1995
Date: Wed, 5 Jul 1995 14:53:51 +0200
From: Osmann 
Reply to: Asymetrix 'Toolbook' product discussions
     
To: Multiple recipients of list TOOLB-L 
Subject: CLIPDLL

Subject: CLIPDLL

Hi, everyone:

I wrote a DLL for ToolBook which enables you to save the actually selected objects in a file and secondly allows to read this file and put the objects back to your book. These functions are very fast, because they are based on API clipboard functions.

The functionality is very simple: I copy the selected objects in with "send copy" into the clipboard and move the correct memory area into a file.

In the other direction I read the file into a global memory area, tell the clippboard to use this memory as it's content and make a "send paste"!

The functions in the DLL "clipdll.dll" are the following:

                LONG  ClipToFile (WORD,LONG,STRING)
                LONG  FileToClip (WORD,LONG,STRING)

The parameters are:

                WORD: sysWindowHandle   (ToolBook's window handle)
                LONG: ClipFormat        (the registration-number of ToolBook's clipboard format)
                STRING: filename (where to store or where to get the objects)

ClipToFile stores the selected objects in the specified file and FileToClip reads the objects from a file and pastes them into your book. In current version the return value of the functions do not inform about succes or fail of the funtions!

The appended example shows how to use this funtions and how I solved the problem to get ToolBook's clipboard registration. Especially for for this problem I hope that someone has a better solution. The file clipdemo.exe" contains the DLL "clipdll.dll" and the example "fileclip.tbk".

I think that this DLL could solve a lots of problems (growing exe problem...) and enhance ToolBook with a completely new feature!

The actual version of this DLL is not save, that means I would advice everybody not to use this DLL in his applications before it has been tested completly (in this version no correct error codes are returned), but I'm strongly interested in every feedback (How does it make sense to use it? Problems in usage? Comments?). If someone's interested in the source code for this DLL and wants to help me in making it save (I'm not very skilled in windows-programming) he should contact me!

**********************************************
* Harald Osmann                              *
* Software Developer                         *
* TUEV Rheinland, Germany                    *
* Phone:   Germany 2151-441438               *
* Fax:     Germany 2151-441438               *
* E-mail:  sd008ja@unidui.uni-duisburg.de    *
**********************************************