#include "steam/mobject/session/locatingpin.hpp"

Description

helper for the (preliminary) position resolve() implementation.

we can't sensibly reason about tracks, because at the moment (10/07) we lack a track implementation...

shouldn't we use a range-restriction LocatingPin (subclass) to represent the to-be-found solution? (ichthyo: see Trac #100)

Definition at line 140 of file locatingpin.hpp.

Public Attributes
TimeVar	minTime

TimeVar	maxTime

Fork	minTrack

Fork	maxTrack

bool	impo

Public Member Functions
	LocatingSolution ()

Time	getTime ()
	get some time value which could stand in for this solution.

Pipe	getPipe ()

bool	is_definite ()

bool	is_impossible ()

bool	still_to_solve ()

Constructor & Destructor Documentation

◆ LocatingSolution()

LocatingSolution ( )

inline

Definition at line 148 of file locatingpin.hpp.

Member Function Documentation

◆ getTime()

LocatingPin::Time getTime ( )

get some time value which could stand in for this solution.

This doesn't imply this value is a solution, It's just a value we can use. At the moment (10/07), LocatingSolution is implemented as interval, and we return the lower bound here.

Definition at line 143 of file locatingpin.cpp.

References LocatingPin::LocatingSolution::minTime.

Referenced by LocatingPin::resolve().

Here is the caller graph for this function: