Remark: only general questions are listed here.
For technical questions about AddFlow ActiveX, see the FAQ in the help file installed with AddFlow.
For technical questions about AddFlow for .NET, see the tutorial.doc file installed with AddFlow for
.NET.
FAQ AddFlow for .NET
1. What is AddFlow for .NET?
AddFlow for .NET is a .NET Windows Forms Custom control. It provides
approximately the same flowcharting/diagramming features as the
ActiveX version and also some new features, more flexibility and
a simpler and more powerful object model. It has been
completely rewritten in C# to take advantage of the
infrastructure provided by .NET. It is 100% Managed Code.
2. Is it compatible with the ActiveX version?
AddFlow
for .NET is NOT compatible with the current ActiveX version. For instance, if
you are porting an application from VB6, you will have to review almost all the
code that uses AddFlow (however this is just a matter of a few hours).
If you need a strict compatibility, you can use the current ActiveX version
(5.4) as a COM component in a .NET application. However we encourage you to use
the .NET version which is far more powerful and easier to use.
3. What has changed?
AddFlow for .NET is still
easier to use since its programmatic interface has been changed towards more
simplicity.
The "user data" properties (Marked, UserData, Tag, VariantTag, Key)
are removed. We just keep a Tag property allowing attaching any object to a node
or a link. However, if you still need such properties, you could add them by
deriving the Node or the Link class. We provide the "DeriveNode"
sample illustrating how to do that for keys. Another easier method is to use the
PropertyBag.
Also the Picture property is removed. We just keep the PictureIndex property
which is renamed ImageIndex.
The persistence methods (LoadFile, SaveFile, Copy, Paste, CanPaste) are removed.
Instead, we encourage you to use either the IXMLSerializable interface, either
the XMLFlow component.
Also some properties are grouped: for instance, the Shape and ShapeOrientation
properties of ActiveX version are grouped in only one property, Shape,
which is an object of type Shape which contains 2 properties: Style (Rectangle,
Ellipse, Hexagon, ...) and Orientation (North, East, ...).
And finally, there are also some new properties (Items collection, SelItems
collection, AntiAliasing property, etc) and also all the inherited properties,
methods and events.
There is a conversion guide in the tutorial provided with AddFlow.
4. What are the concrete benefits of using the .Net version instead of the ActiveX version?
The ActiveX version of AddFlow can be used as a COM component in a .NET application because COM objects are supported
in .NET (however just as 16-bit programs are supported under 32-bit Windows!). We think anyway that, in the .NET environment,
it is better to use a .NET component. Moreover AddFlow for .NET offers some concrete benefits:
-
the possibility to derive the Node and the Link classes to obtain new objects that fit your needs
-
anti-aliasing technology to obtain smoother diagrams
-
custom shapes for nodes and arrows
-
SVG support
5. What is the license agreement for AddFlow, LayoutFlow?
The key points are the following:
- each product is licensed per individual developer.
- each product is runtime royalty free.
- the evaluation version of each product has a nag screen.
You may use it for up to 60 days for trials and design-time
evaluation purposes only.
6. Can I use it in a web page?
AddFlow
for .NET is a windows form control, not an ASP control. It
executes on the client, not on the server.
However, Internet Explorer supports the OBJECT tag for hosting
ActiveX controls. In .NET, the OBJECT tag can be used to also host
Windows Form controls and provide accesses to the properties of
the hosted control. See the paragraph 2.3.3 of the tutorial
to see how to use AddFlow in a web page.
7. What platforms does AddFlow for .NET support?
Our product works on those platforms with .NET
support, namely, the following platforms,
Microsoft Windows® 98
Microsoft Windows NT® 4.0 (SP 6a required)
Microsoft Windows Millennium Edition (Windows Me)
Microsoft Windows 2000 (SP2 Recommended)
Microsoft Windows XP Professional
Microsoft Windows XP Home Edition
8. What are the benefits of using AddFlow for .NET?
Small
deployment assembly, suitable for use on the Internet. The size of the
Lassalle.Flow.dll file is just 316 Kb.
Small programming interface: we have always preferred the quality to the
quantity. We refuse to provide an inflation of classes and properties.
Full integration with the .NET environment.
Great Flexibility.
Runtime royalty free.
FAQ AddFlow ActiveX
1. Under what development tools has AddFlow ActiveX been tested?
AddFlow has been tested under Visual Basic (version 5 and 6), Visual C++ (version 5 and 6),
Delphi (version 3, 4 and 5) and IE5.
VB, VC++ and Delphi samples are provided in the AddFlow installation package.
If you project to use AddFlow with another development tool, then you should be very
careful and make all the needed tests before purchasing the control.
2. How to use AddFlow ActiveX in a web page?
AddFlow can be incorporated in a web page. Your HTML code needs to reference the control as an object. The CODEBASE
tag tells the browser where to find the control. You can use a CAB file here.
Since you can't distribute the license file, you need to create a run-time license using LPK_TOOL.
See the "Internet application" topic in the help file for more informations.
3. Is AddFlow ActiveX digitally signed?
Yes AddFlow is digitally signed, using Microsoft Authenticode technology and Verisign as the certifying authority.
4. What is the difference between the evaluation version and the licensed version?
It is the same version, i.e the same files, the same installation package that you can download from this web site.
If you register, you'll receive a license number which is a kind of unlock key.
The evaluation version, after being purchased, is turned into the full retail
product by use of this electronic unlock key.
5. I have installed a licensed AddFlow version but the nag screen is keeping on appearing. Why?
First remark:
Even if you have installed a licensed version of AddFlow,
the executables that have been created before with the
evaluation version, will keep on displaying a nag screen.
To remove the nag screen, you have to regenerate them
with the licensed version.
Remark if you use VC++:
If your development
environment is VC++, then there are two cases to consider:
- if you use AddFlow in a dialog box, then, with the Resource editor, you should remove the AddFlow
control and place a new AddFlow control again (for each
window dialog box AddFlow).
- if you use AddFlow in a view, see the Microsoft KnowledgeBase Q151771
and see the CAfEditView::OnCreate function if the afEditView.cpp module
of the C++ afEdit sample provided with AddFlow.
Remark if you use AddFlow in IE:
To avoid the license nag screen, see
the AddFlow help file: click on "Tutorial" then on "Internet
Application" and read the "License File" paragraph.
If the previous remarks do not help
you, then we suggest:
- uninstall AddFlow,
- remove all addflow4.ocx and addflow4.lic files from
your PC.
- reinstall AddFlow again (do not forget to enter your AddFlow
serial number)
Then you should check that:
- the license file addflow4.lic has been created in your
windows\system directory.
- the ocx file (addflow4.ocx) is in the same directory as
the license file.
- the ocx file has been registered by the installation
program.
If it is not the case, you can do that yourself with the
following command:
REGSVR32 ADDFLOW4.OCX
And finaly, your problem may be also due to a corrupted serial number. In
such a case, you may email us.
7. What shared DLLs are required for AddFlow ActiveX to work?
AddFlow is a MFC (Microsoft Foundation Class) based ActiveX control, compiled with Microsoft VC++ 6.0.
It requires the 3 following Microsoft shared DLLs:
- MFC42.DLL
- MSVCRT.DLL
- OLEPRO32.DLL
Those 3 DLLs are provided in the AddFlow installation package.
8. What is the license agreement for
AddFlow ActiveX?
The key points are the following:
- each product is licensed per individual developer.
- each product is runtime royalty free.
- the evaluation version of each product has a nag screen.
You may use it for up to 60 days for trials and design-time
evaluation purposes only.
FAQ Graph Layout components
1. What is a graph layout?
The primary purpose of those tools is to offer a way to display graphs or flow charts
in a reasonable manner, following some aesthetic rules.
2. Can we use HFlow, OFlow, SFlow or TFlow without AddFlow?
Currently, HFlow, OFlow, SFlow and TFlow are AddFlow extensions and you cannot use them without AddFlow.
Typically, you can first create your nodes and links inside AddFlow,
using the AddFlow API, giving each node a random or a (0,0) position.
Then you call the layout method of the graph layout control of your
choice. This method will position the nodes and the links in a
reasonable manner in the AddFlow control, following some aesthetic
rules that depend on the choosen control (hierarchical with HFlow,
symmetric with SFlow, ...)
If you just want to perform a layout on a graph without displaying
them in an AddFlow control (for instance because you have already a
way to display the diagram), then you can use both a hidden AddFlow
control and the graph layout control, for instance HFlow, to do that.
In such a case, AddFlow is just used to store the logical structure of
the graph and to retrieve via its API, the resulting positions of its
nodes and links.
3. Will your Graph Layout controls be sold separately and for what price?
We sell them separately because we think that a company may be interested in one type of Graph drawing, for
instance hierarchical drawings, and not be interested by the others.
See Ordering informations.
4. What is the license agreement for HFlow, OFlow, SFlow, TFlow?
It is the same as for AddFlow.
|