• Any 8/16/32-bit CPU; only an ANSI "C" compiler is required.
• Any (monochrome, grayscale or color) LCD with any controller supported (if the right driver is available).
• May work without LCD controller on smaller displays.
• Any interface supported using configuration macros.
• Display-size configurable.
• Characters and bitmaps may be written at any point on the LCD, not just on even-numbered byte addresses.
• Routines are optimized for both size and speed.
• Compile time switches allow for different optimizations.
• For slower LCD controllers, LCD can be cached in memory, reducing access to a minimum and resulting in very high speed.
• Clear structure.
• Virtual display support; the virtual display can be larger than the actual display.

Find out more information...

• Complete window management including clipping. Overwriting of areas outside a window's client area is impossible.
• Windows can be moved and resized.
• Callback routines supported (usage optional).
• WM uses minimum RAM (app. 20 bytes per window).

Find out more information...

A display driver supports a particular family of display controllers (typically LCD controllers) and all displays which are connected to one or more of these controllers. The driver is essentially generic, meaning it can be configured by modifying the configuration file LCDConf.h. The driver itself does not need to be modified. This file contains all configurable options for the driver including how the hardware is accessed and how the controller(s) are connected to the display.

Find out more information...

• Simulation plus viewer.
  

Bitmap converter... find out more...
Font converter... find out more...

A dialog box (or dialog) is normally a window that appears in order to request input from the user. This widget is included in the Window Manager/Widget package which is optional.

Find out more information...

Memory device contexts allow creation of a section to output to the display in the memory of the CPU. All drawing operations can be used. When the image has been build completely, it is transferred to the display in a single operation, allowing flicker free updates even with slow CPUs or slow displays.

Find out more information...

More and more graphic controller manufacturer (Fujitsu/Toshiba) offer a flexible layer concept. The multiple layer/multiple display feature allows you to access more than one layer. It also allows you to use multiple displays in your embedded application. This feature is part of the basic package. You do not need additional software to use the multi layer support. Right now up to 5 layers/displays can be supported.

Find out more information...

• Widgets (window objects, also known as controls) are available. They generally operate automatically and are simple to use.

Find out more information...

VNC stands for "Virtual Network Computing". It is, in essence, a client server system based on a simple display protocol which allows the user to view a computing 'desk- top' environment not only on the machine where it is running, but from anywhere on the Internet and from a wide variety of machine architectures. Client and server communicate via TCP/IP. emWin VNC support is available as a separate package.

Find out more information...

A simulation environment under MSVC++ is available. It can be used to write and test the entire user-interface on the PC (all routines are 100% identical to your embedded application, no matter what CPU or LCD you are using). This makes debugging and development easy and convenient. Generating screen-shots of the LCD is a snap. These screenshots can then be inserted into documentation. emWinView, a separate program shows the contents of the simulated LCD even during debugging.

Find out more information...

Using the MCU/CPU as LCD controller.

Find out more information...

Touch screen support for analog touch panels is available. This includes a low level driver,which handles the analog input (from an 8 bit or better AD-converter), debouncing and calibration of the touch screen. The window manager deals with touch messages and widgets such as button objects. It takes no more than one line of code to create a button or another widget, which then automatically handles touch messages and reacts accordingly.

Touch Screen Simulation

The touch screen simulation is integrated into the regular emWin simulation. Mouse events are used to simulate the touch screen. The simulation can be used to write the user interface of your application and can be send as a simple exe file to anybody for discussion, demonstration or verification.

Touch-screen & Mouse Support

• For window objects such as the button widget, emWin offers touch-screen and mouse support.

Find out more information...

Antialiasing is the smoothing of lines and curves. It reduces the jagged, stair-step appearance of any line that is not exactly horizontal or vertical. emWin supports dif- ferent antialiasing qualities, antialiased fonts and high-resolution coordinates. It is an optional package.

Find out more information...

"Ready-to-go" starterkits allow you to work on real hardware and get familiar with emWin as well as with the microcontroller and other development tools.

Find out more information...

Request for your FREE Segger 30-day Evaluation here...