[misterhouse-users] impact of mht->xml on floorplan attributes

[Chris W. <cwi...@wi...>]

With particular regard to the floorplan attributes, the mht spec seems 
to associate the floorplan coordinates to a group.  However, the 
implementation ties them to the item being defined.  When I convert the 
mht to xml, I'm currently bringing the floorplan coords forward as part 
of the group, but now wonder if they should be item level coordinates 
instead?

an illustration follows (noting that set_fp_location is called for 
attic_fan, not Garage)...

the following (table A) format mht:
X10A,       C2,     attic_fan,             
Appliances|Outside|Garage(15;15)

generates the code:
$attic_fan                           =  new X10_Appliance('C2', );
$Appliances                          =  new Group;
$Appliances                          -> add($attic_fan);
$Outside                             =  new Group;
$Outside                             -> add($attic_fan);
$attic_fan                           -> set_fp_location(15,15,1,1);
$Garage                              -> add($attic_fan);

the current xml is:
	<item>
		<type>X10A</type>
		<address>C2</address>
		<name>attic_fan</name>
		<group>Appliances</group>
		<group>Outside</group>
		<group fp_loc="15,15">Garage</group>
	</item>


I'm thinking the fp_loc is actually an attribute for the item, and not 
the group.
I don't really use the floorplans yet, so I don't have first hand 
experience/input for this.

Chris.