• State Verified Answer
  • Replies 17 replies
  • Answers 1 answer
  • Subscribers 436 subscribers
  • Views 9224 views
  • Users 0 members are here
Options
Related

Studio behaviour when clicking a file

Jörg Heinemann

Hi all,

I had already sent this question to my local contact but she referred to this support website:

Either by new installing Studio 2015 or by an update of Studio 2014 one of the properties of Studio 2014 was changed, and I need to know how to get back to the former version:

Before this change it was possible to click on a project- or package file and open the file in Studio. If you now click on a sdlproj or sdlppx file, Studio 2014 opens – or opens again, if already running, in a second instance– but without opening the file in only of both instances. Instead opening only works by opening the file from the application’s menu “Open project” or “Open package”.

Windows standard is that clicking on a file opens not the application but even the file you have clicked on. So I don’t understand why Studio now has a behaviour which is not standardlike.

Is there any one who knows how to to change Studio back?

I am working with Windows 10.

Thanks in advance.

Jörg
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
  • 0

    Hi Jörg,

    If I have understood your question, this is how Studio has always behaved and it is not contrary to Windows functionality.
    If you want to open an sdlxliff file in one step, you have to click on the sdlxliff file itself, which is exactly how files behave in other Windows applications.

    However, that would not be useful if the sdlxliff file is already part of a project, as a second project file (.sdlproj) would be created in the same folder as the sdlxliff file.
    To open a file within a project, you have to first open the project. That is logical.

    Then you can open the sdlxliff file by clicking on it in the list in the 'Files' view in Studio. 

    Also, when you have a project that contains multiple sdlxliff files, you may only wish to open one at a time and it would be therefore very inconvenient if Studio automatically opened them all at once. Particularly if you actually wanted to open them together as a virtual merge file, very useful if files contain repeated content that can then be autopropagated, saving you time and improving consistency. You can do this by highlighting all the files you wish to open, right-clicking and selecting 'Open for Translation' (or '...Review' if you're proofreading).

    Finally, you mentioned opening a second instance of Studio. This can be done deliberately by clicking on your Studio icon again and can be useful, for example if a large file is taking a long time to verify, you can open Studio again and start work on the next job in your workload.

    Hope this helps,
    Ali
  • 0 in reply to Alison Field
    Hi Ali,

    Thanks for your reply. But it seems that I haven’t described the problem in the right way. So I will try once more:

    Before: Clicking on a sdlproj file (an existing Studio project which I have created on computer A and which ist saved on the server and now should be worked on with computer B) opened (1) the Studio application (if not running yet) and (2) inside Studio the project. So I only had to click on the project in the Studio project list and the Studio file list opened. When Studio already was running, the system switched over to the application (instead of opening the application) and (2) as above.

    Now: Clicking on a sdlproj file opens the Studio application (if not running yet) and the project no longer comes up in the project list, or the application opens in a second instance (if already running) but neither here the project is to be found in the project list. – So for opening a new project you now always have to open the Studio application first and then you have to open the wished sdlproj file from inside the program – and this is no typical Windows behaviour (e.g., when you click on a docx file Word opens and the file is opened too).

    It may be necessary to have a second instance of the Studio application but this is not the standard situation and should be happen only if intended.

    The same as I have described with sdlproj files happens with sdlppx files.

    What is about sdlxliff files I don’t know, that is not the way I work; I always use projects. So your explanation doesn’t really help; perhaps you could have a second look on my description of the behaviour change?

    Kind regards,

    Jörg
  • 0 in reply to Jörg Heinemann
    Hi again Jörg,

    Ah, I think I understand now. You're talking about GroupShare server-based projects?

    If so, someone else will have to answer you as my work and experience is not server-based. Sorry!

    If not, the behaviour you describe is not how Studio is supposed to work...

    Ali :)
  • 0 in reply to Alison Field
    Hi again, Ali,

    No, not GroupShare server-based project I mean but my own server projects. I have a (cloud-based) server, and sometimes I create the project on the notebook in the morning, and afterwards I work further with this project on the desktop PC.

    But fine to see that you agree that the behaviour is not the one Studio should have.

    So perhaps someone else has any idea (and this behaviour I have met on more than one computer on which I had installed Trados 2015 [but still working with 2014 which I even have adjusted as default application for sdlxxxx files]).

    Jörg
  • 0 in reply to Jörg Heinemann
    Hi Jörg,

    It is probably not of any help but on my PC the behaviour is how it is supposed to be. Projects are also on a server drive and when I double click the sdlproj file, the project is added to the project list in the Studio instance that was already active. I'm on 2015 CU3 (not sure though if it is still in beta or if it has been officially released).

    cheers,

    Annemieke
  • 0 in reply to Annemieke Jennissen
    Hi Annemieke,

    Not really helpful but encouraging – perhaps the problem will be solved when switching to 2015.

    Thanks!

    Jörg
  • 0 in reply to Jörg Heinemann

    Hi Jörg,

    I know an agency who have worked to a network server with Studio 2009, 2011, 2014 and now with Studio 2015 and they have not had this problem. It sounds to me as if it is something in your set-up that is causing this. That means that even with Studio 2015 you might have the same thing happening unless the problem is solved.

    If you haven't already, could you try this on whichever computer/s this is happening on:

    With all instances of Studio CLOSED, go to:

    C:\Users\username\AppData\Roaming\SDL\SDL Trados Studio\10.1.0.0 (for Studio 2011)
    or
    C:\Users\username\AppData\Roaming\SDL\SDL Trados Studio\11.1.0.0 (for Studio 2014)
    or
    C:\Users\username\AppData\Roaming\SDL\SDL Trados Studio\12.0.0.0 (for Studio 2015)

    By 'username' I mean your user profile name.
    If you can't see 'AppData' you'll have to 'unhide' system folders to do it.

    Then delete:

    BaseSettings.xml
    Plugincache.xml
    UserSettings.xml

    Delete these 3 files in whichever of the above folders is relevant to the version/s of Studio you have had this problem with on that machine (and any other this has occurred on).

    Reopening Studio will automatically recreate these xml files. There's no need to save them elsewhere or rename them unless you really want to.

    I don't know if this will help but it's worth a try.

    All the best,
    Ali
  • 0 in reply to Alison Field
    Hi again, Ali,

    I will try but first I would like to have a further view into these files. It seems that some settings should be saved elsewhere for otherwise I have to restore to much (for example the autotext suggestions etc.).

    Thanks a lot.

    Kind regards,

    Jörg
  • 0
    Jörg, did you manage to resolve this issue? I'm having the same problem with Studio 2014 SP2 as follows:

    I work in an LSP, so we save projects on our (physical) server, allowing any user to access them. This is outside of Groupshare, which we do not run. Previously it had the desired behaviour - Double-clicking an sdlproj file created by another user would open the project in the project view. If a copy of Studio is not already running, it launches Studio first, then opens the relevant project. If not, it opened the project in the instance I was already running.

    This was good. All was well.

    Over the last two weeks, my computer was operated by another user who did something. I don't know what she did. I don't think she nows what either. This 'something' removed all of Studio's file associations, meaning that you'd need to 'Open with' in order to get them to run in Studio as requred. When I set this up, I saw that the files were producing the behaviour described by Jörg, whereby they launched a new instance of Studio, but failed to do anything else.

    I reinstalled Studio. However, this has not solved the problem. Effectively, the behaviour is exactly the same as if I double clicked on the Studio 2014.exe file rather than the file I want to open. It worked fine before, and I have reinstalled Studio to try and solve the problem, so I wonder if it is a problem with Windows or with Java.

    I have tried Ali's proposed solution of deleting the settings xml files, to no avail.

    I wonder if anyone knows what might have caused this or what might solve it.
  • 0 in reply to Richard Davis
    Hi Richard,

    I forgot if the problem was solved – I have had already at the time of my first question here a license fot Studio 2015. Since then, I guess, I have installed the upgrading and work now with Studio 2015 SR2. Now this problem doesn’t happen any longer to me.

    So I can’t give you any hint how to change.

    Lycka till, kolay gelsin, gutes Gelingen!