Introduction !DrWimpC Features DrWimpC library Examples


!DrWimpC Wimp Lib Action Menu




Since this manual was written a new method of application/DrWimpC library interaction has been introduced that is more flexible and code efficient. The Template Function (Objects) facilities. The method described here is the same as used by the BASIC DrWimp library and still can be used, but is no longer the default. When DrWimpC App Builder creates an application it no longer creates any default user files, but only does so if the WimpLib Action menu is used by selecting one or more user functioons and files. The advantages of using Template Function (Objects) is to reduce code source and object size by only requiring the functions your application uses need to be defined instead of using whole files of default function definitions, and more importantly shared libraries of Tenplate Function objects are possible which potentially further reduces code size (and maintenance) by their reusability.

The User Functions can still be used with or without Template Functions. The WimpLib Action menu is described briefly here. There is more innformation on using it and user functions in the web site pages.

This menu lists the wimp library categories of actions handled by the DrWimpC library. For each item there is a sub menu listing the standard user source files required for the action to be successfully used in your application. Each source file contains default function definitions for each user function called by the DrWimpC library action for a particular action. I.e. the functions that the linker will try to find when producing the final !RunImage. By clicking SELECT on a menu item you indicate that your application will include the wimp library action in iots features and processing. The item will have a tick against it if all the user source files are present in your application's main C source directory. You can then load the files into a source editor by clicking <SELECT> on their name, or use the The Source File Action Submenu to get a function list of a file, and click on a function in the list to load the source into a source file editor with the caret placed at the beginning of the code of the function selected.

The greyed out items in the menu are standard wimp events where the BASIC DrWimp library has no action, consequently the DrWimpC library does not do anything with them. Note also, that some items in the list are do not have equivalents in the BASIC libary e.g. The External Edit and Ram Transfer Protocol handlers. At the time of writing some of these additional items are initially coded into the DrWimpC library, but have not been tested, and so should not be used yet. These are the External Edit Editor (the External Edit client handling has been tested), The Selection and Clipboard models and Drag and Drop handlers.

The default files directories and resources are stored in an application named !DRWDEF that should be placed in either Boot:Resources or the same place as the GCC 4 !Sharedlibs. You can edit these (but not create or delete) to your own requirements so that each time one is copied into your application it will already have these edits done. For this release, the following Wimp Lib Actions are included in a an applicaton when you first starr specifying user functions for it, along with default Standard User C source Files required by the DrWimpC Library. Some of the default files appear in more than one user file list, since they are required by more than one wimp library action.

Minimum Wimp Lib Actions Included in a New Application

.

[Top]