Re: Don't use full display / Spare a little border
- From: "Valter Minute [eMVP]" <valter.minute@xxxxxxxxxxxxxxxxxxx>
- Date: Mon, 21 Dec 2009 15:20:25 +0100
On 12/16/2009 11:32 AM, David S wrote:
Hi,
Maybe this Group isn't the correct.
I use an TI-OMAP3530 (with Board Support Package from BSquare) and it works good.
On our hardware design we use a display with 800x480px. This display is Landscape (We want to use this display later in Portrait mode) and has a bigger border for the backlight LEDs on the lower side. Our device is in small size, so the border for the LEDs is masked by the box. For design reasons the opposite side of the display is masked too, so the display is cut a little bit (30 lines) on the upper side.
In the device driver for display I can set the timing parameters for front and back porches, so I have added a higher timing for the porch instead of the pix data. This generally works, so Windows only use the small area of the display. But the display doubles the very last line for the spared area. So I have the typical windows gray of the taskbar (other side) in the area I want to spare... This is a problem, because the "box" (actual it is the panel for the touch) is black but don't cover the display with 100%, I can see a little bit the gray pixs due to transparency.
Is there a better solution to "cut" the display, i.e. Windows paint the remaining pixels black? After I rotate the screen, this spared area will be the right border...
You can handle this in your video driver (adding an offset to the memory area used by the system as "video memory" and configuring the "stride" of your display (the size in bytes of a row of pixel that may not be equal to the exact size of a row calculated by simply multiplying the number of pixels by the bit per pixels).
A platform independent solution requires a customization of Window CE UI (supported by GWES) to implement your own version of the NonClientView_t::BoundingRect function, forcing a different size for top-level windows and leaving them out of the non-visible area.
There is an (old) article from Mike Hall and Steve Mailled about this topic on MSDN:
http://msdn.microsoft.com/en-us/library/aa459146.aspx
--
Valter Minute (eMVP)
Training, support and development for Windows CE:
www.fortechembeddedlabs.it
My embedded programming and cooking blog:
www.geekswithblogs.net/WindowsEmbeddedCookbook
Windows Embedded support forums in Italian:
http://social.msdn.microsoft.com/Forums/it-IT/windowsembeddedit/threads
(the reply address of this message is invalid)
.
- References:
- Don't use full display / Spare a little border
- From: David S
- Don't use full display / Spare a little border
- Prev by Date: Re: USB mass storage device asynchronous file change notification
- Next by Date: Re: Wear Leveling support in NOR Flash - WinCE 6.0
- Previous by thread: Don't use full display / Spare a little border
- Next by thread: CETK on Windows CE and Mobile for the NDIS IM Driver
- Index(es):
Relevant Pages
|
