History of IMAGE

== Syntax ==

:ctl[n]: IMAGE(Class Specific Properties), Other Properties

== Description ==

:The class IMAGE allows the filter designer to place a bitmap in the dialog window. The bitmap will be transparent according to the top-left pixel color. By default, this user control is not actionable.

== Class Specific Properties ==

:NOTIFY

::Makes the user control actionable and activates tooltip.

:SUNKEN

::Draws a half-sunken border around the image.

== Other Properties ==

:Val

::Assigns a value to the image, but only when it is disabled. (default = 0)

== Example ==

<code>

ctl[0]: IMAGE, Image="Logo.bmp"

ctl[1]: IMAGE(MODALFRAME), Image="aa.bmp"

</code>

== Notes ==

:Once the image is actionable, its value definitions are lost. The reason is that an action returns a specific value and overwrites (once the mouse button is clicked over the image) the image's value.

:Currently only BMP files are supported.

:When standalone filters are created, images are not embedded by default. You can use the Embed: function to embed the icon into the standalone filter file.

:The image file should be present in the active directory or in any of the directories set in the PATH or FM_PATH variables (check your AUTOEXEC.BAT file).

:IMAGE also supports the Common Control Styles, such as BORDER, NOBORDER, TABSTOP, GROUP, VISIBLE, DISABLED, MODALFRAME, MOUSEOVER, MOUSEMOVE and more.

== Also see ==

:BITMAP, ICON, METAFILE