The way do to it for graphic display is to return a full screen bitmap. Custom characters won't work for graphics displays I'm afraid.

If you do look at it - I suggest you read the display API page in the technical infomation section on 6.2 (part of the help pages). Please use display hash rather than the previous bitmap method to speed things up a bit.

Yes each byte controls 8 pixels in a vertical row. To get good speed on a slow server, you probably want to pre build the bitmaps for a snow flake at each vertical position. Then when you want to build a frame it is simply a matter of bitwise-or ing bitmaps together.

So the idea would be to define a bitmap for a snow flake (probably one for SBG and one with more pixels for SB2). [Bear in mind that on the graphic displays the first byte is a vertical column, but this does not matter if your shape has rotational symmetry] Then build bitmaps of this shape at each virtical offset you want - nb this bitmap only needs to be as wide as the flake.

Then when you want to display a frame, you traverse each horizontal line bitwise oring together the appropriate 2 bytes (SBG) or 4 bytes (SB2) for that column for each flake which appears in that column. Produce a byte string which represent the whole screen and then send it to $client->update() as a bits component of a display hash [or have it return by the lines function].

Let me know if you plan to look at this and want more help.

Adrian

----- Original Message ----- From: "Craig, James (IT)" <[EMAIL PROTECTED]>
To: "Slim Devices Discussion" <[email protected]>
Sent: Thursday, September 15, 2005 4:45 PM
Subject: RE: [slim] Re: Snow saver for new graphic display


Based on what's in SlimTris, I can see how to display a custom
full-screen bitmap using the "bits" key value,
Although this is a rather painful format - seems like each hex character
controls a group of pixels?

It would be ideal if one could overlay this on top of the usual 2 line
display but I can't seem to make that work,
Seems to be either the bits or the lines, not both?

James
--------------------------------------------------------

NOTICE: If received in error, please destroy and notify sender. Sender does not waive confidentiality or privilege, and use is prohibited.
_______________________________________________
Discuss mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/discuss
_______________________________________________
Discuss mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/discuss

Reply via email to