'FINDING.DAT
'===========
'essentials as always

INPUT,  see03.sc1
OUTPUT, test
DIR


'We've already seen some examples of FIND in Coloring and Lighting
'discussions.  Recapping we've found all stuff of a particular
'color:

FIND, COLOR, 12       

'and we've found ALL stuff in a particular group:

FIND, ALL   

'but there are several other finds we might want to do.

'Sometimes we might want to find all big stuff:
'Since the range of visibility is roughly related to size of
'an element; we can use

FIND, RANGE, 64

'where all objects (in a particular class) having a range of
'at least 64 FS units (always in FS units) (see the report file
'generated to get a listing of the ranges for each element)
'will be found.

'For buildings we can use the height as a find criterion:

FIND, HEIGHT, 200

'This will find every element (buildings) 200 feet high or more

'But the trickiest (and most powerful) find is to locate a
'single specific element.  It's actually very easy:

FIND, NUMBER, 3
COLOR, 12, 15, 6
ROAD

'will find and color the third road in the scenery file.
'However; the tricky part is to know that you want the
'third one!  See the discussion below.

'OK; that's enough for this lesson.
SAVE
END

Discussion:  There are several ways to determine what the number of
the element is that you want to change.  Let's say there is a specific
polygon that you would like to handle in a special way (give it distinct
day, dusk and night coloring).

You can find it's number by having kept a record during entry (the
first is #1, second #2 and so forth). This is an extremely good prac-
tice but not available if you are using someone else's scenery (or if
you are human).

Second method is to go into the edit mode of the ASD editor and deselect
all groups except the one of interest (polygons, in this case) and hit
the TAB key.  You will now be at polygon #1.  TAB again for #2 and so
on.  This is good for small numbers of things but... well, you know.

The third method is to investigate the report file generated by SEE
during any execution.

TIP: if you want a report only, you can use SEE's EZC mode along
with a /R on the command line following the path and filename:

      SEE03 C:\FS4\SCENERY.SC1 /R<enter>

This will create a report named EZC.RPT

Look through the section listing the polygons and use the positions,
ranges (normally proportional to size), and colors to identify the
polygon you are interested in.

Best bet is to use all three methods.

The other thing to be aware of in working with element numbers is
that when you edit out an element all the later elements' numbers
are decreased by 1.

SEE will normally only alter something once.  Therefore if
your first set of commands changes ALL the lines to have dusk and night
colors, you are not going to be able to then change all the blue lines to
taxiway lights (because as far as SEE's concerned there are no longer
'any (pure) blue lines to change.  So the moral of this story is that you
must do the most specific changes first before doing the general ones.

Other commands use the principle of element number along with object type:
export, delete, setrange, locate.