#549 Fragments to be removed not colored correctly

3.5
closed-fixed
Interface (55)
5
2015-12-03
2012-11-25
khagaroth
No

When using mouse to move to a string, the fragments to be removed are not correctly highlighted until a keyboard input is initiated. This is not such a big problem as it works correctly when advancing using the keyboard, but I guess fixing it wont hurt.

Discussion

  • Didier Briel

    Didier Briel - 2012-11-25
    • status: open --> pending
     
  • khagaroth

    khagaroth - 2012-11-25

    Win 7 x64. Note that by moving to a string I mean advancing from one active string to another, not copying text by drag and drop like in the other bug.

     
  • khagaroth

    khagaroth - 2012-11-25
    • status: pending --> open
     
  • Didier Briel

    Didier Briel - 2012-11-26

    Thank you for the clarification: so,by "moving to a string", you mean double-clicking on a segment. So, what do you mean by "the fragments to be removed"?

    Didier

     
  • khagaroth

    khagaroth - 2012-11-26

    Options - > Tag Validation -> (bottom) Fragments that should be removed...

    For example if I add '\[fuzzy\]' to highlight the fuzzy marker (which BTW should IMHO be the defualt behavior) in the string, it doesn't get highlighted after the string is activated when using mouse doubleclick, but it IS highlighted if I activate the string using keyboard.

     
  • Didier Briel

    Didier Briel - 2012-11-26

    Thank you, I understand now.

    Didier

     
  • khagaroth

    khagaroth - 2014-12-07

    This is still a problem btw, but now it doesn't color the strings to be removed at all. This was the case even before the custom color introduction and I hoped it would be fixed with it introduced, but that's unfortunately not the case.

     
  • Aaron Madlon-Kay

    Fixed in r7397. I wasn't able to reproduce the difference in behavior between double-clicking a segment and entering via keyboard.

     
  • Aaron Madlon-Kay

    • status: open --> open-fixed
    • assigned_to: Aaron Madlon-Kay
    • Group: --> 3.5
     
  • Didier Briel

    Didier Briel - 2015-12-03
    • status: open-fixed --> closed-fixed
     
  • Didier Briel

    Didier Briel - 2015-12-03

    Closed in the released version 3.5.3 of OmegaT.

    Didier

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks