You are currently working on UAT 

Question for input (outside current beta process!) on Studio editor behaviour

Hi all,

I have a quick question on how you use the Editor in Studio. We recently (re-)discovered the behaviour that you always have a lag of approx. 1 second when using the mouse to click in a segment other than the currently active one. We were now wondering if that is still required in this day and age, or if we could change it to be instantaneous in a future release.

A bit of background: originally, we thought that a small lag might be useful to allow the user e.g. do a double click or drag/select text without the segment getting active. This would then e.g. allow you to stay in the current segment as active but e.g. quickly copy/paste content from another target segment and paste it in the active one, without the other segment to get active, perform lookups etc.

In a recent experiment, I was looking at a build where the lag was no longer present - and I thought that this made the Editor feel 'snappier' when navigating with mouse clicks. But I was wondering if we can make the change just like this or if there are use cases where our user community would feel that they would still need that lag for your use cases.

I hope the question is clear enough - and am looking forward to your feedback and input!

Thanks

Daniel

Daniel Brockmann
Team Trados @ RWS

Parents
  • Interesting question Daniel. As others have said, I'd like to try both versions out, and preferably have a permanent setting allowing us to switch between the two and adjust the speed.

    I just checked, and the lag is indeed useful if I want to quickly double click on a word in a non-active segment and copy it. If it got activated the second I clicked in it, this would not really be useful.

    How about this: Change it so there is no lag, but … allow the user to activate the lag ad hoc by holding down the shift key before clicking in a non-activated segment (for cases where the lag would be useful)? Everyone happy.

    Michael

Reply
  • Interesting question Daniel. As others have said, I'd like to try both versions out, and preferably have a permanent setting allowing us to switch between the two and adjust the speed.

    I just checked, and the lag is indeed useful if I want to quickly double click on a word in a non-active segment and copy it. If it got activated the second I clicked in it, this would not really be useful.

    How about this: Change it so there is no lag, but … allow the user to activate the lag ad hoc by holding down the shift key before clicking in a non-activated segment (for cases where the lag would be useful)? Everyone happy.

    Michael

Children
No Data