glados.no/_files/sound/bss/london/manual/MAIN/MAINDesign_tree.htm

112 lines
6.2 KiB
HTML
Raw Blame History

<!doctype HTML public "-//W3C//DTD HTML 4.0 Frameset//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
<meta name="generator" content="Adobe RoboHelp 9">
<title>Design tree</title>
<link rel="StyleSheet" href="HtmlHelp.css" type="text/css">
<style title="hcp" type="text/css">
<!--
p.hcp1 { font-size:10pt; }
h2.hcp2 { font-size:10pt;
font-weight:bold; }
span.hcp3 { font-weight:bold; }
p.hcp4 { font-size:10pt;
font-weight:normal; }
-->
</style>
</head>
<body>
<h1 class="firstHeading">Design tree</h1>
<p style="font-size: small;"><img src="Design_tree_2.jpg" alt="" style="border: none;" width="300" height="406" border="0"></p>
<p class="hcp1">This palette helps the designer to locate any
used design object within the design file. This is a comprehensive selection
device using a folder tree similar to Windows Explorer, enabling the location
of everything from hardware devices down to individual controls within
control panels. The tree is organised by various categories of design
object types to aid in finding items.</p>
<p class="hcp1">If an object selected in this list is within
a currently visible design window then a single click will locate and
highlight it. Design items can even be found in hidden windows - you don't
even have to be in the same layout; in this case double click the item
to locate it. London Architect will open the correct window and highlight
the object.</p>
<p class="hcp1">This tree is probably the single most important
tool used by programmers to build custom control panels. This allows the
programmer to quickly navigate around the complete list of controls and
graphics available in the default control panels and select elements to
incorporate in the custom panels. This eliminates the cumbersome task
of navigating around the design file and opening different processing
objects to access controls, info boxes or graphics for copying.</p>
<h2><a name="Design_Categories" id="Design_Categories"></a>Design Categories</h2>
<div id="bodyContent">
<h2 id="siteSub" class="hcp2">This Computer</h2>
<p>Allows the designer to assign objectives such as logging out of
Architect, show docking windows, online / offline selection or even
quitting the application, to control objects.</p>
<h2 class="hcp2"><a href="Control_Panels.html">Control
Panels</a></h2>
<p class="hcp1">Shows default and custom Control Panels.</p>
<h2 class="hcp2"><a href="BLU-10&#32;Programming&#32;and&#32;Operation.html">BLU-10
Set-Up Pages</a></h2>
<p class="hcp1">This is a nested tree showing all the folders
and pages for any BLU-10s in the design.</p>
<h2 class="hcp2"><a href="Devices.html"><span class="hcp3">Devices</span></a><span class="hcp3"><a
name="Devices" id="Devices"></a></span></h2>
<p class="hcp1">This tree starts with the selection of
hardware devices and works down through their associated configurations
of processing objects, parameters and settings.</p>
<h2 style="font-size: 10pt; font-weight: normal;"><span class="hcp3">CobraNet
Bundles</span><a name="Cobranet_Bundles" id="Cobranet_Bundles"></a></h2>
<p class="hcp1">Shows activated CobraNet bundle settings,
as shown in the CobraNet edit box in the Properties for a CobraNet
input or output block in the Configuration window.</p>
<h2 class="hcp2">System Layouts<a name="System_layouts"
id="System_layouts"></a></h2>
<p class="hcp1">This is a nested tree; enabling selection
of both the Main design window (from any other starting window) and
its associated zones. Further down the tree are the hardware devices
used in the system and, within them is displayed information relating
to the hardware box's settings for display, date and time and 3 wire
mode operation of the logic control ports. Also shown is a list of
the configurations set up for each device; these contain links to
all the processing objects used and their associated control panels.
Finally hardware settings for the IO cards and control ports are displayed.</p>
<h2 class="hcp2"><a href="MAINPresets.htm"><span class="hcp3">Presets</span></a></h2>
<p class="hcp1">Displays a list of all the parameter and
venue presets in the current design.</p>
<h2 class="hcp2"><a href="Links.html"><span class="hcp3">Links</span></a></h2>
<p class="hcp1">Displays a list of all the links in the
current design</p>
<p style="font-size: 10pt; font-weight: bold;"><a href="Key_Bindings.htm"><span class="hcp3">Key Bindings</span></a></p>
<p class="hcp4">Displays a list of
all Key Bindings in the design. &#160;Key bindings are a way of using
keys on your PC keyboard or any external keyboard to control any of
the parameters within your HiQnet London Architect design file.</p>
<p style="font-size: 10pt; font-weight: bold; color: #000080;">Documents</p>
<p class="hcp4">This enables you to
add any file(s) to your .architect file which will then be saved with
the design file. &#160;You should be aware that adding documents to
the design will increase the size of the file which could hinder the
<a href="Save&#32;To&#32;Device&#32;Network.html">Save to Device Network</a> capability
if the file becomes very large. Right-click on the documents folder
in the design tree to add then edit or delete documents. Multiple
documents can be added at once. &#160;<EFBFBD>Edit<EFBFBD> will mark the file as
write-able and then attempt to open the document using the registered
application for edit. If there are no applications registered to edit
the document, then the document will just be opened instead. This
may or may not allow the document to be edited. The <20>open<65> command
sets the document to be read-only and opens the document in the application
associated with reading it. <span style="font-size: 10pt; font-weight: normal;">Be
careful when saving an architect file if you have any documents open,
as any document changes may not get saved with the architect file.
When a document is added to London Architect a copy is taken of the
original, therefore any edits made to the document will have no effect
on the original.</span></p>
</div>
</body>
</html>