Two minor issues I'm seeing with the recently added feature to move performers using the arrow keys...
Both have to do with when the performers are selected.
1) If the timeline is not on a set or subset and then performers are selected, pressing the arrow keys causes the timeline to jump the nearest previous set and the selected players are moved (in the direction based on the arrow key pressed) from that Set location.
example: the timeline is in between Sets 3 and 4; select some players; press the up arrow key; the result is that the timeline jumps to Set 3 and the selected players are moved back a step from their original position on Set 3. I expected the arrow keys to have no effect when pressed when the timeline is not on a Set or Subset.
2) The arrow keys don't work if the performers are selected when the timeline is not on a Set or Subset, even after moving to a Set of Subset on the timeline. Other performer editing features, like the marbles, work if you initially select performers when the timeline is not on a Set or Subset. This isn't the case with the arrow keys.
example: the timeline is in between Sets 3 and 4; select some players; move the timeline to any Set; press the up arrow key; the result is that the selected players do not move. I expected the arrow keys to move the selected players.
Arrow keys when performers selected on non-set
Re: Arrow keys when performers selected on non-set
Hi bjindrich,
Thanks for the reports. These issues will be fixed for the next release.
Have a great day!
William
Thanks for the reports. These issues will be fixed for the next release.
Have a great day!
William
Re: Arrow keys when performers selected on non-set
Found another scenario where the arrow keys don't work: after performing a revert - performers that are reverted are still selected, but the arrow keys don't work.
Re: Arrow keys when performers selected on non-set
Thanks bjindrich,
That scenario will also be fixed in the next release. The original issue was one of focus. When you clicked on the timeline the window that handled the key presses wasn't receiving them any more. The handler for those elements has been moved so that it is accessed globally.
William
That scenario will also be fixed in the next release. The original issue was one of focus. When you clicked on the timeline the window that handled the key presses wasn't receiving them any more. The handler for those elements has been moved so that it is accessed globally.
William