The absolute steering worker shares 90% of the core code with the relative move steering worker apart from recent updates. It hasn't been used much of late because I believe the Sony VISCA camera's inability to track reliably to a specified coordinate. However VAPIX API cameras are very simple to target and for the large are the recommended cameras.
Rather than updating the absolute steerer with all the recent changes and maintaining duplicated code, this ticket will merge them into a single implementation that can be configured to use absolute targeting. The raison d'etre for this is that the relative move steerer can overshoot the target in some circumstances and we wish to see if absolute moving can help resolve the issue.
In principle, it is all working at least using the Dummy Camera. Unfortunately when our V5918 AXIS (VAPIX) cameras are told to move to an absolute coordinate and then another before the first move completes it will first stop before move to the second target. This means that tracking a moving target leads to jerky "stop-start" movements.
I tested this a while back with VISCA Vaddio cameras, and the movement was also quite jerky.
I think unifying the two is probably still valid as we don't know how other camera's will operate and maybe there are workarounds that can be applied to the camera drivers.