<Graphic [N,N [,N,N]]>
<gr [N,N [,N,N]]>
<bmp [N,N [,N,N]]>
<JPEG [N,N [,N,N]]>
<jpg [N,N [,N,N]]>
G switch alternative where the text of a frame becomes the name of a .BMP file. The first optional pair of Ns
specify the top left corner location (if only the first Ns
are provided then the XYJustification rules will apply), the second pair the bottom right (scaling the image as needed), four zeros signifies full screen, -1 uses a default value (like the width of the image), values can be real as per <x> and <Y> switches
(although <x> and <Y>
are deprecated these days and the use of
<xy> is strongly recommended). If the Ns are used they override any <X> and <Y> switches, also use of the second pair of Ns will override any <BMPMultipliers>. See the Digital Video section for details on the use of the Ns.
With the addition of the Independent JPEG Group's
libjpeg library DMDX can now read JPEG images. Without the use of the variant <JPEG> keyword the extension .JPG or .JPEG will have to be specified in the frame's text, otherwise all <JPEG> does is change the default file extension from .BMP to .JPG.
The default positioning of graphics is slightly different than the default
positioning of text, typically the bottom of the text is in the center of the
screen but graphics are centered such that the middle of the graphic is in the
middle of the screen. So if you want to combine the two I recommend overriding
the default positioning for both of them and use specific coordinates for all
frames with <xy .5,.5>
<xyjustification center> in the parameters.
NOTE: There is a bug in libjpeg that causes it to
leak memory each time a JPEG is loaded. The amount of memory appears to
fluctuate between 12 kilobytes and 58 kb, rather trivial for most systems (hence
it's going unnoticed for more than a decade) however if thousands of JPEGS are
<MediaLife> is not used to reduce
image reloading then you can in fact use all the free heap and cause DMDX to
throw an out of memory error. Only other thing to do is convert your JPEGs
to BMPs as loading BMP files does not leak memory.
NOTE: Filenames must not contain leading or trailing spaces as they'll
be used as part of the file name and will cause DMDX to fail to open your image.
As of version 220.127.116.11 of DMDX extended characters
(like Hebrew, Chinese or Arabic ones) can be used in the file name as long as
the Unicode option is in use.