VrOne
|
ON-LINE REFERENCE DOCUMENTATION CARDINAL SYSTEMS, LLC 386-439-2525 |
Function Keys
“The art of mapping is the art of organizing complexity.”
- Anonymous
Function keys are the most important aspect of
VrOne data collection. Taking the time to properly set up function keys before
a project has started will save hundreds of hours of production time.
In many ways VrOne is just another CADD
system. It has an insert
line command and it has an insert symbol
command. And so does every other
mapping system.
Function keys are the method of making a mapping
system out of a CADD system. Instead of
using insert line to place a road, the operator will
used a mapping key such as PavedRoad.
PavedRoad will assign all the desired parameters and behavior to Insert Line and start it.
Function keys reduce the amount of knowledge the
mapping professional needs to know about VrOne. They simply choose the feature they want to collect and go.
Function keys are named. These names may be keyed in, placed in
macros or even placed in other function keys.
The name of the function key file to use must be
set in the VrOne configuration program (vrcfig). It is possible to have multiple function key files but only one
can be active at a time.
Creating and Editing Function Keys
In the above dialog box a function key called Building is being created. The line that is placed by this function key will be a squared, un-fonted white line placed in layer 19.
Function Keys
Lists the currently defined function keys. A key may be selected and its parameters will be displayed to the right. If multiple keys are selected, the function key starter settings can be applied to all of the selected keys.
Key name
The reference name of the function key. This name may be keyed in, placed in a macro or on another function key.
Vr function
The VrOne application to start when the key is executed. The proper Line, Symbol or Text tab will be selected depending on the type of VrOne command selected.
Key num
The reference number of the function key. This number may be keyed in, placed in a macro or on another function key.
Description
Function key description. This is for information only.
Function key starter settings
The items in this section control the display of the labels in the function key starter dialog.
Line Tab
Line parameters that will be assigned when the function key is executed.
Symbol Tab
Symbol parameters that will be assigned when the function key is executed.
Text Tab
Text parameters that will be assigned when the function key is executed.
Local Args
These commands will be executed when the function key is started. Normally local commands are placed here. For example, if the Insert Symbol command is started by a key and the symbol rotation needs to be turned on then ROTMODE=1 would be entered on the Arguments line. Multiple commands may be entered separated by a comma.
Global Args
These commands will be executed when the function key is started and when the function key is woken up after being overlaid. Normally global commands are place here.
For example, consider the state of a global command such as snap:
· Contour is started and it sets snap to end point (SnaEnd).
· Drive overlays Contour and sets snap to intersect (SnaInt).
· Drive is terminated and Contour wakes up and becomes active.
· Since snap is global, the state is snap is now intersect. This is a state that Contour did not intend.
Placing SnaEnd in the Wake up command of Contour ensures the state of this global parameter is what is expected.
Assoc cmd1 and cmd2
Associate commands allow function keys to be linked. In many cases there may be several function keys used to insert a certain map feature. One might put in a line and another may put in text.
For example, consider the operation of inserting a parking area. This feature consists of line that will define the parking edge and a text label of “Parking Area”. There are two function keys defined which are ParkLine and ParkText. The associate command 1 of ParkLine has be set to ParkText as follows:
|
Assoc
cmd1 |
Park Text |
· ParkLine is started and the parking lot edge is collected.
· Ac1 is keyed in and the ParkText starts and “Parking Area” is labeled.
· ParkText is terminated and ParkLine continues collecting the parking lot edge.
On end cmd
The on end command allows one function key to execute a key-in, a macro or another function key each time an entity is saved.
For example, consider a spot elevation. This feature consists of a symbol and a text label. There are two function keys defined as follows:
SpotX Places the spot elevation X.
SpotElev Places the elevation of the previously read symbol.
The On end command of SpotElev is set as follows:
|
On end
cmd |
SpotText |
When the spot elevation symbol is placed, the On end command will start Spot Text.
The On end command of SpotText is set as follows:
|
On end
cmd |
Pop |
The Pop command tells VrOne to terminate the current application (command) that is at the top of the application stack.
· SpotElev is started and the spot elevation location is digitized.
· SpotText starts automatically and the elevation of the first point is labeled.
· SpotText terminates due to the On end Pop statement
· SpotElev wakes up and the next spot elevation is ready to be read.
There are more parameters that would need to be set to make the spot elevation functions keys work as expected but the above example shows how to chain function keys together.
On quit cmd
The on quit command allows one function key to execute a key-in, a macro or another function key when the function key is ended.
Export
The export button is used to export the function key definitions to a comma-delimited file, typically with a .csv extension. This file can be edited with a text editor or spreadsheet and then imported back in.
Import
The import button is used to import the function key definitions from a comma-delimited file. These files typically have a .csv extension.