Yes, the Intel Array Visualizer object mode is very different than the Compaq product. The Compaq Avis2D ocx has a flat organization: >100 properties and methods and no contained objects. By contrast the Intel AvGLGraph organizes the graph state into collections of objects. For example, the state related to the virtual viewpoint is contained in the Camera object. So setting up the camera position would look like this:

graph.Camera.Viewpoint(Avis.Objmod.AvCoord.AV_XCOORD) = 1.5 graph.Camera.Viewpoint(Avis.Objmod.AvCoord.AV_YCOORD) = 1.9 graph.Camera.Viewpoint(Avis.Objmod.AvCoord.AV_ZCOORD) = 0.6

To me the Intel interface seems much easier to work with since related properties are grouped together. Also, it makes it easier to support collections of objects. E.g. a graph that contains 4 XYPlots.
A good place to get started with the new object model is the object model diagram in the documentation.

We'll try to add more samples in the next release. Anything in particular that you are looking for? Since the number of languages that can be used with the Intel OCX has increased (VB6, VB.Net, C#, C++) creating a new sample in each language is a lot of work. The only feasible thing to do might be for new samples to be implemented in one language (C#?) and leave conversion to other languages as an execise to the reader.

Another way to see how the AvGLGraph control works is to look at the data files that ship with the product. If you save the file to XML, you can then open the XML file in IE and inspect all the property settings that make up each graph.

John