RenderingType

Output human readable ascii HTML representing a ProEssentials charting ActiveX to be instantiated on the client, creating a destination object to receive data and interact with the user. The HTML rendered is similar to...

ImageUrl property should be set to point to a secondary Webform (i.e. Webform2.aspx) with a ProEssentials WebForm control with its RenderingType set to BinaryActiveXStream. Thus the above DATA attribute points to the secondary Webform which prepares binary data representing the default state of the instantiated ActiveX. When the web page is shown to user, it contains a charting ActiveX in a default state prepared via ASPX page pointed to by ImageUrl.

Optionally, instead of having a primary ASPX page (i.e. WebForm1) with a ProEssentials Webform with its RenderingType set to ActiveX, you could simply embed the above object tag within an ASPX/HTML page. See Chapter 3 Overview for a list of ClsIDs.

Streams compact binary data (non-human readable data) to a client-side ProEssentials ActiveX.

The target ActiveX could be the result of a primary page (i.e. Webform1) containing a ProEssentials Webform with its RenderingType property set to ActiveX, or via an OBJECT tag. See above.

It's important that the ASPX page containing a ProEssentials Webform control with this setting contain no ascii or html as part of the page. As any ascii will be passed along to client and corrupt the binary data. The ASPX page should contain only an object tag and server-side executable code.

Streams compact binary data (non-human readable data) to a client-side ProEssentials ActiveX.

Used with client-side ActiveX LoadFromUrl method to update chart without refreshing page. LoadFromUrl should point to an ASPX page containing a ProEssentials WebForm with its RenderingType property set to BinaryDataStream.

It's important that the ASPX page containing a ProEssentials Webform control with this setting contain no ascii or html as part of the page. As any ascii will be passed along to client and corrupt the binary data. The ASPX page should contain only an object tag and server-side executable code.

Streams compact binary data (non-human readable data) representing the bits to a PNG or JPG depending upon the RenderedImageType property.

The target image could be the result of a primary page (i.e. Webform1) containing a ProEssentials Webform with its RenderingType property set to ImageMap, or via a simple IMG tag. See below.

It's important that the ASPX page containing a ProEssentials Webform control with this setting contain no ascii or html as part of the page. As any ascii will be passed along to client and corrupt the binary data. The ASPX page should contain only an object tag and server-side executable code.

Output human readable ascii HTML representing an IMG/MAP tag. The HTML rendered is similar to...

The MAP tag is only generated if the ProEssentials Webform enables any hot spots. These will become clickable areas within the image. See PeImageMap for more info.

ImageUrl property should be set to point to a secondary Webform (i.e. Webform2.aspx) with a ProEssentials WebForm control with its RenderingType set to BinaryImageStream. Thus the above SRC attribute points to the secondary Webform which prepares binary data representing the bits to the image. When the web page is shown to user, it contains an image (with potential dynamically generated map coordinates) with bits dynanically produced via a secondary WebForm. Two forms of dynamically generated content is produced, ascii IMG/MAP items, and binary image bits. Thus the need for a primary and secondary ASPX page.

Optionally, if MAP items are not necessary (no hot spots enabled), instead of having a primary ASPX page (i.e. WebForm1) with a ProEssentials Webform with its RenderingType set to ImageMap, you could simply embed the above IMG tag (minus MAP items) within an ASPX/HTML page.