A: Rotation is a demo version limitation. The full version does not rotate the flow charts.
A: That is a demo version limitation. The full version does not add anything extra to the flow charts.
A: Yes, with Editor.
A: Yes. Visio export requires Visio installed. Visustin sends the flow chart data to Visio, which is responsible for creating the diagram. Exporting does not function without Visio.
A: Detailed flow charts are large indeed. Several smaller charts are better than a really big one. Use the Structure tab to flowchart your code in parts. Hide comments to preserve space. Read more about handling large charts.
A: No, there is no fixed size limit. Very large flow charts are not practical, though. They don't fit in documents or allow reasonable print-outs. Make several smaller charts to visualize a complex file. More about large charts.
Earlier versions of Visustin had some problems with code sizes exceeding 3000 lines, 32 kB or 64 kB, but these limits have been lifted.
A: Yes, but be prepared that the graphs will be very large. Your wall may not have be long enough for hanging up the print-out.
A: Visustin does not do this. It is a detailed flowcharting tool. Flow charts work on the statement level displaying each branch, loop and so on. Flow charts are not for viewing higher-level (less detailed) relationships, such as procedure-to-procedure or module-to-module dependencies.
If you use Visual Basic, VB.NET or VBA, try Project Analyzer to visualize procedure calls, file dependencies, class hierarchies and the control flow at a higher abstraction level.
A: You should get another diagramming program for that purpose. Flow charts are detailed on purpose. Their idea is to display every branch, jump and loop. Other diagram types display an overview with less detail. That's not what Visustin does since it's a flowcharting program.
A: Comments are not a part of a program's control flow. They may be written at a location that is hard to link with a specific control flow, or even on a line that is not executed at all. Therefore, a comment in the flow chart may appear at a different location from what the developer was thinking when writing the comment. Sometimes it is not clear whether a comment next to a conditional statement is labeling the "if" condition or the "then" branch. Similarly, a comment next to a looping statement may describe the entire loop, the loop body or the loop condition. A comment above a case label may describe the previous case branch, the case label itself or the next case block.
A: We rely on user feedback to understand which languages need support. See Add new language to check out the options.
A: Visustin is a stand-alone tool that doesn't depend on any programming environment or IDE. If you would like Visustin to work as an add-in, please send us your vote.
A: No. Visustin produces UML style Activity Diagrams in a way that is not compatible with other UML tools.
A: No. Visustin only produces UML style Activity Diagrams.
A: No. Visustin is incompatible with XMI.
A: Visustin is an artificial name with the intended meaning visualizer. It is formed from the Latin word visus (vision) by adding then Finnish ending -tin (-izer). So, we simply added the words visus+tin = Visustin. While Visustin itself is a mixed language construct, the Finnish word visusti means carefully, a requirement for professional software development and maintenance.
Visustin is pronounced as [visustin].
Written in another way, say it like vi-sus-tin. The "i" and "u" sounds are short as in "it" and "put". The ending "tin" sounds like tin the metal in English.
Some misspellings of Visustin include "Vistuin", "Visusting", "Visustion" and "Visutin".
See Troubleshooting.