[Bug 409] motion control components do not have 'standard' constructor ( for dynamic loading)

For more infomation about this bug, visit

Ruben Smits <ruben [dot] smits [..] ...> changed:

What |Removed |Added
--------------------------------------------------------------------------
Status|NEW |ASSIGNED
CC| |ruben [dot] smits [..] ...
Target Milestone|--- |1.4.1

--- Comment #1 from Ruben Smits <ruben [dot] smits [..] ...> 2008-01-18 15:54:59 ---
(In reply to comment #0)
> All nAxes components take an extra argument, besides the name, denoting the
> number of axes. This non standard constructor prevents these components to be
> dynamically loaded by the DeploymentComponent.
> All Cartesian components take an extra argument, besides the name, denoting a
> property filename. This non standard constructor prevents these components to
> be dynamically loaded by the DeploymentComponent.
>
> This can be dirty-fixed by creating a new constructor or setting a 'default'
> value to the number of axes or property filename. The clean-fix is to make the
> number of axes and property filename a property and implement configureHook()
> which checks this value and resizes the work vectors and/or reads the property
> file.
>

A fix is already committed on trunk for the naxes components.

A patch for the cartesian components will follow.

Ruben

Ruben Smits's picture

[Bug 409] motion control components do not have 'standard' const

For more infomation about this bug, visit

Ruben Smits <ruben [dot] smits [..] ...> changed:

What |Removed |Added
--------------------------------------------------------------------------
Status|ASSIGNED |NEW
AssignedTo|orocos- |ruben [dot] smits [..] ...
|dev [..] ... |