On Sat, 4 Apr 2009, Tom Russo wrote:
Because nobody has gotten around to coding up the ability.
What it will require is for someone to code up a way to turn a CAD object into
a multiline object. There is a currently-unused routine that can take
a list of lat/lon pairs and generate the multiline string and a point at the
center (average lat/lon), and it could be used for that. But someone will need
to do the GUI work to allow specification of which CAD object to send out
this way, and assemble an object to go out over the air.
We also need to add a more general capability: A way to specify
which objects get transmitted (public), and which are local
(private). Some data used in a search or EOC may be sensitive.
These CAD objects as well as existing types of objects need to be
represented in Xastir such that it's impossible to confuse their
public/private state, yet make it possible to switch an object to
the opposite state. Of course these individual object states need
to be persistent across crashes/restarts as well.
--
Curt, WE7U. archer at eskimo dot com
http://www.eskimo.com/~archer
Lotto: A tax on people who are bad at math. - unknown
Windows: Microsoft's tax on computer illiterates. - WE7U.
The world DOES revolve around me: I picked the coordinate system!"
_______________________________________________
Xastir mailing list
[email protected]
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
