Context Navigation

Changes between Initial Version and Version 1 of Ticket #9447, comment 8

initial	v1
11	11	Yeah, I'm struggling to think of a situation where the relative would be useful, other than when you're seeing real-time output and want to nudge it manually but that doesn't really fit the ways the commands are used, at least through ffmpeg and sendcmd perhaps libav world is different?
12	12
13		Implementation wise: a mode or secondary property to target for relative rotation could use the flow in '''process_command''' as it stands at the moment whereas absolute rotation via mode or the default properties could reset the '''rot_quaternion''' prior to '''ff_filter_process_command'''?
	13	Implementation wise: a mode or secondary property to target for relative rotation could use the flow in '''process_command''' as it stands at the moment whereas absolute rotation via mode or the default properties could reset the '''rot_quaternion''' (But not the filter rotation context) prior to '''ff_filter_process_command'''?
14	14
15	15	I appreciate that this is designed to make some use cases more pleasant and prevent the users getting into recoverable but confusing situations - but I think it's undeniable that there's a tension between this behaviour - how commands and users expect to update filter parameters, and what makes the most sense in defining scripted reprojection.