The various specifications how some MObject is to be placed (logically) within the EDL are given by small LocatingPin objects forming a chain. For resolving the actual position, at the moment (10/07) we use a preliminary implementation to support the most common Placement types (fixed and relative). It is comprised of the nested LocatingSolution and the functions FixedLocation::resolve(LocatingSolution&) and RelativeLocation::resolve(LocatingSolution&) etc. If this is to be extended, we'll need a real spatial discrete constraint solver (and this probably will be some library implementation, because the problem is anything but trivial).
Definition in file locatingpin.hpp.
#include "proc/common.hpp"
#include <utility>
#include <tr1/memory>
#include <boost/scoped_ptr.hpp>


Go to the source code of this file.
Namespaces | |
| namespace | asset |
| namespace | mobject |
| namespace | mobject::session |
Classes | |
| class | mobject::session::LocatingPin |
| Positioning specification, possibliy chained to further specifications. More... | |
| struct | mobject::session::LocatingPin::LocatingSolution |
1.5.6