COMFILE Technology's Documentation Library

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Hosting jControls ======

To overcome the graphical limitations of Windows CE and the .Net Compact Framework, jControls CF35 employs an entirely different graphics pipeline.  For the jControls to appear properly with transparency, alpha blending, z-ordering, etc... developers will need to add jControls to containers that support that graphics pipeline (e.g. [[.:jForm]] and [[.:jContainer]]).  

===== Hosting jControls with the jForm =====

The simplest way to host jControls is with the [[.:jForm]].  Simply use Visual Studio's ''Add'' --> ''New Item'' menu to open the //Add New Item// dialog.  There, in the //jControls CF35// category you can find the //jForm// default template.

{{ .:addnewjform.png?nolink |}}

That will add a new ''jForm'' to your project which can serve as a container for hosting jControls.

A ''jForm'' can also host other .Net Compact Framework controls, but those controls, if placed behind jControls, will not appear through the transparent pixels of the jControls.  By placing other controls in front of jControls, or by preventing overlap entirely, all controls can co-exist together on a ''jForm''.

{{ .:jcontrolswithdefaultcontrols.png?nolink |}}

===== Hosting jControls with the jContainer =====

Similarly, adding jControls directly to a generic .Net Compact Framework ''Form'' will not expose the ''Form'' through the jControls' transparent pixels.  To overcome that limitation, jControls can be placed in a [[.:jContainer]], and will appear correctly.

<html><center></html>**Appearance in Visual Studio**<html></center></html>
{{ .:containerdesigntime.png?nolink |}}

<html><center></html>**Appearance in Windows CE**<html></center></html>
{{ .:jcontrolsondefaultform.png?nolink |}}