You are currently working on UAT 

  • Replies 7 replies
  • Subscribers 433 subscribers
  • Views 1166 views
  • Users 0 members are here
Options
Related

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

Daniel Brockmann

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

Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • Hello Daniel,
    the question is very interesting, and I think answering would require a test.

    For sure there's the need to feel the editor "snappier", despite the numerous latest improvements there are still some laggy moments that could ruin the perception of a fast editor.
    For sure there's the need to not start unwanted processing that gets activated when a segment becomes active when you don't want to.
    Maybe it could be possible to move the waiting time (the small lag) from the activation of the segment to the activation of the slower tasks like lookups and such...

    In the way I'm used to work when reviewing segments and performing correction this waiting time is highly perceived, while in translating segments in sequence this small lag is not a big deal.

    Editing Source is really laggy, but I don't do that that often.

    Could it be possibile to have a beta with an option to activate/deactivate the segment activation time in order to test it?

    Thanks to you and SDL for the effort into making Studio faster and reliable. This is very appreciated.
Reply
  • Hello Daniel,
    the question is very interesting, and I think answering would require a test.

    For sure there's the need to feel the editor "snappier", despite the numerous latest improvements there are still some laggy moments that could ruin the perception of a fast editor.
    For sure there's the need to not start unwanted processing that gets activated when a segment becomes active when you don't want to.
    Maybe it could be possible to move the waiting time (the small lag) from the activation of the segment to the activation of the slower tasks like lookups and such...

    In the way I'm used to work when reviewing segments and performing correction this waiting time is highly perceived, while in translating segments in sequence this small lag is not a big deal.

    Editing Source is really laggy, but I don't do that that often.

    Could it be possibile to have a beta with an option to activate/deactivate the segment activation time in order to test it?

    Thanks to you and SDL for the effort into making Studio faster and reliable. This is very appreciated.
Children
No Data