Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#673 "Properties..." menu is disabled in team projects

3.1
closed-fixed
None
5
2014-05-19
2014-04-17
Roman Mironov
No

"Properties..." menu and CTRL+E shortcut are disabled in team projects.

Discussion

    • status: open --> closed-invalid
     
  • Didier Briel
    Didier Briel
    2014-04-17

    Disabling it completely was a bit drastic, but it prevents having "incompatible" omegat.project files.

    Didier

     
  • Didier Briel
    Didier Briel
    2014-04-17

    If you need to edit Project Properties (for instance to change something before committing it to the server), you can launch OmegaT with --no-team.

    Didier

     
  • Didier Briel
    Didier Briel
    2014-04-17

    I re-open, because the solution was probably too drastic, as the project manager has no easy way (without using a workaround) to edit project-specific segmentation or file filter settings.

    Didier

     
  • Didier Briel
    Didier Briel
    2014-04-17

    • status: closed-invalid --> open
     
  • This is addressed in r6183. You can now open the project properties dialog with team projects, but all controls are disabled except the File Filters and Segmentation buttons.

     
  • Didier Briel
    Didier Briel
    2014-04-24

    Fixed in SVN (/trunk).

    Didier

     
  • Didier Briel
    Didier Briel
    2014-04-24

    • status: open --> open-fixed
    • assigned_to: Aaron Madlon-Kay
     
  • Roman Mironov
    Roman Mironov
    2014-05-04

    I am probably missing something, but why enable controls for the File Filters and Segmentation buttons when any changes to either cannot be committed to the server? Or is there a way to commit them already?

     
    • Didier Briel
      Didier Briel
      2014-05-04

      You can commit using an SVN client.

      Didier

       
  • Roman Mironov
    Roman Mironov
    2014-05-04

    Thank you for the answer, Didier.

    Obviously, if you change both filters.xml and segmentation.conf, they are overwritten by those from the server soon (upon the next sync at the earliest or reopening the project at the latest). So what you are suggesting is something like this?

    filters.xml - make changes and commit using SVN client before OmegaT syncs and overwrites. This is possible since OmegaT writes this file immediately after you make changes.

    segmentation.conf - do the same. The difference from filters.xml is that OmegaT does not write segmentation.conf until you reopen the project, so you need to do that first, and that means syncing = overwriting the segmentation.conf with the one from the sever. So in theory, there is no way to commit segmentation.conf. However, I noticed that very often, OmegaT often does not overwrite the segmentation.conf when F5 is pressed to reload the project, which makes it possible to actually save segmentation.conf and then commit. (By contrast, when a project is closed and re-opened, OmegaT usually does overwrite segmentation.conf.)

     
    • Didier Briel
      Didier Briel
      2014-05-04

      filters.xml

      Yes. You can temporarily increase the sync time in Options > Saving and Output, so that you don't have to rush to make the commit.

      segmentation.conf.
      You're right, it's more difficult.

      If you have to do a lot of changes upon a period of time, using --no-team temporarily remains more comfortable.

      Didier

       
  • Didier Briel
    Didier Briel
    2014-05-19

    • status: open-fixed --> closed-fixed
     
  • Didier Briel
    Didier Briel
    2014-05-19

    Closing.

    Fixed in the released version 3.1.1 of OmegaT.

    Didier