Context Navigation

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

initial	v1
3	3	It seems like zeroing these when {{{reset_rot!=0}}} is an unintended hold-over from the relative mode which makes sense there as you need to know the change increment not the cumulative value, but here they're better left untouched as long as {{{reset_rot!=0}}}.
4	4
5		In fact it's a surprising side effect when {{{reset_rot>0}}} and any other of the properties except yaw, pitch and roll are changed the view is suddenly clamped back to 0,0,0 - skipping the zeroing of those properties in the siutation where {{{reset_rot!=0}}} would seem to make this reset_rot 'mode' ~~would seem the best solution~~ - and as a side effect make it fully consistent with the old absolute behaviour.
	5	In fact it's a surprising side effect when {{{reset_rot>0}}} and any other of the properties except yaw, pitch and roll are changed the view is suddenly clamped back to 0,0,0 - skipping the zeroing of those properties in the siutation where {{{reset_rot!=0}}} would seem to make this reset_rot 'mode' the most predicatble for users and calling applications - and as a side effect make it fully consistent with the old absolute behaviour.