Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Copy, cut and paste should respect relative position of edit cursor to first selected item #807

Open
Chessel85 opened this issue Nov 5, 2022 · 10 comments

Comments

@Chessel85
Copy link

Hi. Not sure I've fully thought this through but here goes.
A sighted user will likely drag and drop an item to move it. If the mouse arrow is part way along the item at the start of the drag, the mouse arrow is at the same relative position at the end of the drop. In the same way, should or could OSARA capture the distance of the edit cursor from the start of the selected item when a copy or cut is done, and then when the paste happens this relative distance is respected.
This could be the default behaviour as a common way to select items with control left and right arrow places the edit cursor at the start of the item. But doing a shift+A when part way across an item would allow accurate placing of an item at an interesting part of the audio such as a crescendo or the end of the item.
Only problem I can see is what behaviour should happen if the paste would cause the start of the item to be before the project start. Perhaps the paste just doesn't happen.

@tbdalgaard
Copy link

I think free item positioning could help you out here, however I haven't used this myself at all since I find it very confusing for the workflows I have.

Perhaps time selections would do what you are looking for?
So when you copy a part of an item and paste this, later items should be moved if ripple is set properly.

I too wonder if expressions like crescendo can be done via automation... That might help, but I guess it is not what you are looking for.

@Chessel85
Copy link
Author

Chessel85 commented Nov 24, 2022 via email

@tbdalgaard
Copy link

@CastleStarter I am not sure how to get the expected results, so I really hope others will share their thoughts on this. Your idea sounds quite interesting. I just have this feeling that it already can be done, we may just have missed a tini tiny step to get the result you are looking for.

@ptorpey
Copy link

ptorpey commented Nov 25, 2022 via email

@Chessel85
Copy link
Author

Chessel85 commented Nov 25, 2022 via email

@MatejGolian
Copy link
Contributor

MatejGolian commented Nov 26, 2022 via email

@Chessel85
Copy link
Author

Chessel85 commented Nov 26, 2022 via email

@ScottChesworth
Copy link
Collaborator

my suggestion covers placing the start, end or any point in between precisely without needing the nudge dialogue.

It does, and tbh I'm someone who'd definitely use it. However, it's a huge shift in behaviour, and I suspect wouldn't be trivial to implement. The one edge case you've already identified makes me nervous and I'm sure there will be others. I'm not saying no, will leave this open for discussion, but two things need to happen before it moves forward:

  1. The intended UX needs to be fleshed out in plenty of detail, especially around pasting. If we're gonna roll out such a significant change of behaviour, the new UX needs to behave at least as consistently as what we have now.
  2. A contributor who has the chops to implement this if agreed on needs to weigh in on the proposed UX.
    Recently, a lot of time and effort has gone into a feature that might not get over the finish line, in part because the roadmap wasn't clear enough before work started. We don't have the resources for a repeat of that.

@Chessel85
Copy link
Author

Chessel85 commented Nov 27, 2022 via email

@ScottChesworth
Copy link
Collaborator

I can check that and report back.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants