[filefmt.txt 11/97 Digital Insight]

Diagram file format Version 9, for Robochart/OL v8.1 and /XM v2.1

0. NOTES

All fields are ASCII; numeric fields are decimal; lines are 
variable length newline-terminated. There are no separators 
between the sections described below.

A Robochart diagram consists of linked structures of logical objects
(with labels, attributes, etc.) in a hierarchy, associated physical
objects (with image coordinates) that place the logical objects into a
specific diagram level, logical flows (with labels, attributes, etc.), 
and associated physical flows (with vertex coordinates) placing the 
logical flows into diagram levels and connecting physical objects.

Objects and flows are identified in diagram files using small integer
"pool IDs".

1. HEADER LINE

	RCV9 <autolink> <numbering> <window width> <window height>

	RCV9 = file type identifier
	autolink mode: 0=off, 1=zoom-in, 2=full
	numbering mode = 0=none, 1=specified, 2=all

2. FONT LIST

	First line:
		font <# defined> <default> <numbering>

	# defined = number of font definitions following
	default = ID of default label font
	numbering = ID of object numbering font

	Remaining lines:
		<family> <style> <size>
		
	family = name (e.g. "Times")
	style = 0-3; bit 0 = italic, bit 1 = bold
	size in points

4. USER COMMANDS (variable length ASCII lines)

	zero to 9 lines:
		cmd <id> <scope> <command string>
		
	id: 1-9
	scope: 0=current, 1=selected, 2=level, 3=page
		
5. SHAPE PALETTE MAP

	pmap <id1> <id2> ... <id20>

	idN = 0-255 (shape library ID for shape palette)

6. USER-DEFINED SHAPES

	zero to 256 shape definitions (see shapedef.txt)

	(shape ... + 3 or 4 lines each)

7. COLOR MAP

	24 lines:

	color <type> <id> <name> <plotter-pen>

	type = fill, line, or text
	id = 0-7
	name = X color name (or #RRGGBB)
	plotter-pen = HPGL format pen number

8. SIZE OF ALLOCATED POOLS

	pool <logical obj> <physical obj> <logical flows> <physical flows>
	
	values are counts of allocated items + 1

9. PAGE HEADERS

	page <number of pages>
	
	One line per page:
		<root object ID> <child object ID> <phys obj ID> 
			<phys flow ID> <last ID>
	

10. OBJECT AND FLOW DATA

	For each page:
		For each non-empty level:
			<<physical objects>>
			<<flows>>
			<<logical objects>>
			
	<<physical objects>>:
		n <pool ID> <next ID> <logical ID> 
			<X left> <Y top> <X right> <Y bottom> <labelx> <labely>
		
	<<flows>>:
		physical flow:
			f <pool ID> <next ID> <logical ID> <first obj ID> 
				<second obj ID> <# vertices> 
				<attach1> <attach2> <labelx> <labely>
			for each vertex:
				<X> <Y>
		logical flow (if based at current level):
			F <pool ID> <end1> <end2> <op1> <op2> 
				<sfont> <nchar> <refs>
			<<label>>

	<<logical objects>>:
		logical object:
			N <pool ID> <next ID> <type> <op1> <op2> <sfont>
				<nchar> <refs> 
				<parent ID> <child ID> <phys obj head>
				<phys flow head> <num ID> <last ID>
			<<label>>
		<<sub level>>	

	<<label>>:
		label text, "\fxx" = change to font xx,
			"\e" = end, "\\" = "\"

	<labelx>, <labely> = offset from object/flow center
	<type> = object shape ID (0-255)
	<op1> (option byte):
		bit 5-3 = line color, bit 2-0 = text color
	<op2> (option byte):
        	bit   7 = thick line
        	bit   6 = dashed line
        	bit   5 = left justified label
        	bit   4 = visible object border
        	bit   3 = filled (not transparent) object;
				curved flow
        	bit 2-0 = object fill color
	<sfont> = starting font code
	<nchar> = allocated label length
	<refs> = number of physical objects/flows referencing logical
	<last ID> = last ID of child object on sub level
	<end1>, <end2> = flow source/destination end type ID (0-29)
	<attach1>, <attach2> = index of attach point for first/second object