Parents | Children | Properties | Methods | Events |
Purpose: | A graphical object used to represent a bitmap which may be used both to display a picture or as a pattern (brush) used to fill other objects. |
Description
A Bitmap may be created either from a file (.BMP, .GIF or .PNG) or from APL arrays. To create a Bitmap object using ⎕WC, you can either specify the File property or the CBits property, or the Bits and CMap properties.
If you specify File, it should contain the name of a bitmap file from which the bitmap is to be read. If omitted, a .BMP file extension is added. You may also load a Bitmap from a DLL or from the DYALOG.EXE executable. See File property for details.
If instead you want to create a Bitmap dynamically from APL variables, you may do so in one of two ways.
For a palette of up to 256 colours, you may specify the image using the Bits and CMap properties. The alternative is to use the CBits property which works for any size of colour palette.
If MaskCol is non-zero, it specifies the transparent colour for the Bitmap. Any pixels specified with the same colour will instead be displayed in whatever colour is underneath the Bitmap. This achieves similar behaviour to that of an Icon.
The KeepBits property has the value 0 or 1, and controls how a Bitmap is saved in the workspace. A value of 0 (the default) means that the values of CBits, Bits and CMap are not kept in the workspace. If you request the values of CBits, Bits or CMap with ⎕WG, they are obtained directly from the corresponding Windows bitmap resource. When the workspace is )LOADed, the Bitmap is recreated from the associated file defined by the value of the File property. Note that if this file doesn't exist when the workspace is )LOADed, the Bitmap is not created, but no error is generated. However, when you reference the object you will get a VALUE ERROR.
If KeepBits is 1, the values of CBits, Bits and CMap are stored permanently in the workspace, and are used to rebuild the Bitmap when the workspace is )LOADed. In this case, the file name (if any) is ignored. Setting KeepBits to 1 uses more workspace, but may be more convenient if you want to distribute applications.
The Size property allows you to query the size of a Bitmap without having to retrieve the CBits or Bits property and then take its "shape". This will be noticeably faster for a large Bitmap. If you set the Size property using ⎕WS the Bitmap is scaled to the new size.
A useful feature of a Bitmap is that it can be the parent of any of the graphical objects. This allows you to create or edit a bitmap by drawing lines, circles, etc. in it.
The FileRead (90) and FileWrite (91) methods allow you to dynamically manage bitmap files (.BMP). The expression:
bmname.FileWrite
causes the Bitmap called bmname to be written to the file specified by the current value of the File property. The file is automatically written in standard bitmap format. Similarly, the expression:
bmname.FileRead
causes the Bitmap called bmname to be redefined from the bitmap file specified by the current value of the File property.
The MakeGIF and MakePNG methods may be used to convert the image represented by a Bitmap object into a GIF or PNG data stream, suitable for display in a web browser. The TCPSendPicture method may be used to transfer a Bitmap on a TCP/IP socket.
Using a bitmap is always a 2-stage process. First you create a Bitmap object with ⎕WC. Then you use it by specifying its name as a property of another object.
The Picture property specifies the name of a Bitmap to be displayed in an ActiveXControl, Button, Form, Group, Image, MDIClient, Sm, Static, StatusBar, StatusField, SubForm, TabBar, or ToolBar.
The BtnPix property specifies three Bitmaps to be used to represent the 3 states of a Button, Menu or MenuItem.
The FStyle property specifies the name of a Bitmap to be used as a pattern to fill a Poly, Ellipse or Rect object.