[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [lokalize] [Bug 393693] New: You must press Page Down twice to go to the next translation unit on a 
From:       Adrián Chaves <bugzilla_noreply () kde ! org> (Gallaecio)
Date:       2018-04-30 18:43:20
Message-ID: bug-393693-17878 () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=393693

            Bug ID: 393693
           Summary: You must press Page Down twice to go to the next
                    translation unit on a file opened by Pology
           Product: lokalize
           Version: 2.0
          Platform: Other
                OS: Linux
            Status: UNCONFIRMED
          Severity: minor
          Priority: NOR
         Component: general
          Assignee: shafff@ukr.net
          Reporter: adrian@chaves.io
  Target Milestone: ---

tl;dr: Get translation units selected on the Translation Unit pane as soon as
they are opened by Pology.

Tested with a built from sources of commit
ae53fdd92a55bddf355146d2fe3626951c5026eb

No translation unit is selected on the Translation Unit pane when a file is
opened by Pology.

This causes an slightly unpleasant experience: You have to press the Page Down
key twice to go to the next unit, the first press simply marks the first unit
of the Translation Unit pane as selected, and the second press is the one that
actually moves to the next translation unit.

There is something good in the current behavior, however, that may break when
this issue is fixed. If instead of Page Down you use Page Up, you are
immediately taken to the last translation unit.

I believe this is a good behavior because I think that it makes sense for the
last message to have the focus on Lokalize to begin with. Just as the last file
that Pology opens has the focus, the last message of each file that Pology
opens should have the focus as well.

Also, the order in which you would work on the opened files and their
translation units if you start from the first translation unit of each file
(instead of the last) and go down would not match the order in which you would
read the Pology output (not even in opposite order, given the different
behavior for opening files and their translation units). And since Lokalize
cannot currently highlight the parts of the message that caused Pology to open
the message in the first place, you may need to look into the Pology output to
locate the target parts of messages.

-- 
You are receiving this mail because:
You are watching all bug changes.=
[prev in list] [next in list] [prev in thread] [next in thread]