When importing footprints using io_eagle, the following behavior is
expected:
<p>
<table border=1 cellspacing=0>
<tr><th> &nbsp; <th> file contains a single footprint <th> file contains a multiple footprints
<tr>
	<th> library window
	<td> shows up as a single entry in the library window 
	<td> file shows up as a directory in the library window, with the multiple footprints as children nodes

<tr>
	<th> import subcircuit
	<td> imports the footprint as subcircuit into the buffer directly
	<td> pops up a footprint selection dialog with the available footprint
	     names <sup><a href="#fn2">2</a></sup>, loads the selected footprint
	     into the buffer

<tr>
	<th> loading the file directly
	<td> loads one footprint placed on a board<sup><a href="#fn2">1</a></sup>
	<td> loads a board with all footprints placed<sup><a href="#fn2">1</a></sup>
	     (you may want to call a disperse on it)

</table>

<p>
Footnotes: 

<p id="fn1">1. You are not in "footprint edit mode" but "board edit mode"; this is a 
limitation can't be worked around: in eagle there's no header that
explicitly tells apart a footprint from a board.

<p id="fn2">2. Preview can't be rendered because at this point the file is not
really parsed or interpreted, only a map of footprint names is extracted.