Each Bee Mobile control which is inherited from BeeMobile.Common.DoubleBufferingControl (and that is the case for majority of them) uses 3 bitmaps to speed up the drawing.

Symptoms: Properties are missing in Properties pane. Some properties cannot be edited. Properties are dimmed in the properties pane. Descriptions for the properties are missing.

On some Windows CE devices you may receive the error:Can’t find PInvoke DLL ‘BeeMobile.Common.dll’

The presence of PNG image decoder in your OS depends on the presence of SYSGEN_IMAGING_PNG_DECODE variable during the build of OS image.

Based on our experience, if a Windows CE (Windows Compact 7) device fails to draw transparent controls, it is because it is missing AlphaBlend function from its WIN API. AlphaBlend function is present in coredll.dll. During the build of the … Continue reading →

This article describes how to work around the inability to add Bee Mobile iPack CF39 controls to toolbox of Visual Studio 2012 / 2013. Microsoft admits that it is not possible to add custom controls which target Compact Framework v. … Continue reading →

If you want a Bee Mobile control to display a PNG image, you usually have two choices. You can either add the PNG image to the control from your project’s resources or from a file (some controls provide even more … Continue reading →

A lot of people are asking for help regarding PNG image decoding on Windows CE Windows Embedded Compact 7 Windows Embedded Compact 2013 so let’s shed some light into this topic.

You may notice that on some builds of Windows CE, Windows Embedded Compact 7, Windows Embedded Compact 2013 (and other Windows Embedded operating systems) the OS animates the showing (opening) of a form by drawing expanding rectangles animation. While some … Continue reading →

One of major drawbacks of Windows CE is that if you output text to the screen, then by default it is aliased. By putting out a text on the screen I mean putting a control on a form which displays … Continue reading →