• Replies 2 replies
  • Subscribers 391 subscribers
  • Views 316 views
  • Users 0 members are here
Options
Related

Trados Studio 2026: Activating a file already open in the Editor does make it the active file

Josep Condal

In Trados Studio 2026 build 19.0.0.3043, when we try to make active an already opened file in the editor different than the one that is already active, the active file is not changed, that is, the call to EditorController.Activate(document) is ignored.

We also noticed the event hook  EditorController.Opened is not firing the functions that subscribed to it (unlike the EditorController.Opening event hook that fires them fine).

This issue of the active file not being replaced is also reproducible in the Trados Studio 2026 UI with these steps:

  1. In a Trados Studio 2026 with no files opened in Studio, go the Files view of a project and double click on any file to open it. (This works fine: the Editor view opens, and shows the file double-clicked file).
  2. Go back to the Files view and double click on a second file, different from the first one. (This works fine: the Editor view opens, and has the second file as the active one).
  3. Go back to the Files view and double click again on the first file. (This fails:  the Editor view opens, but the second file is the active one instead of the first one).

 Just for the record, none of the above behavior happens Trados Studio 2024. In step 3, Trados Studio 2024 correctly activates the first file.  Also, in Trados Studio 2024 the EditorController.Opened event is fired and EditorController.Activate(document) is honored.
Rate translation
×
Suggest better translation
×

  • Hi  , 

    Thank you for the detailed report, this is now confirmed. We've reproduced everything you described on Trados Studio 2026 (build 19.0.0.3043), both through the API and through the UI steps you listed (opening a file from the Files view a second time does not make it the active file in the Editor).

    To help with triage, we put together a minimal example plugin and can confirm three related symptoms, which all look like they share the same root cause in the EditorController's internal document management:

    1. EditorController.Activate(document) is not honored. In our tests the requested document actually becomes active for a second or two and is then reverted to the previously active document ; so the activation is being undone internally rather than ignored outright. The same reverting behavior is reproducible UI-only via your Files view steps, with no plugin code involved.
    2. EditorController.Opened never fires. Opening fires as expected, Opened does not ; confirmed with per-event counters in the sample plugin (e.g. Opening: 3, Opened: 0 after opening three files).
    3. EditorController.GetDocuments() returns a list of null entries. The list has the correct count, but the entries are null, which makes it impossible to obtain document instances to pass to Activate(document). As a workaround we're capturing the document instances from the ActiveDocumentChanged event instead.


    All three behave correctly in Trados Studio 2024, so this is a regression in 2026.

    The reproduction sample is available in the Sdl-Community repository on the Studio_2026 branch under Code samples/CustomViewExample ; it includes ribbon actions that demonstrate each of the three issues with diagnostics in the message boxes and trace output.

    +  ,   ; tagging you to get this triaged; given it also affects the built-in Files view behavior (not just the public API)

    Patrick Andrew Hartnett | Developer Experience | Team Lead | RWS Group

  • in reply to Patrick Andrew Hartnett

    Hi   - just as an update, we are tracking this as LG-54585 and have put it in scope of the first cumulative update in Trados Studio 2026 Release (timing TBA, tentative August/September). Thanks, Daniel

    Daniel Brockmann
    Team Trados @ RWS