Bug 360877 - Various UI issues when editing Title Clip
Summary: Various UI issues when editing Title Clip
Status: RESOLVED FIXED
Alias: None
Product: kdenlive
Classification: Applications
Component: User Interface (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Jean-Baptiste Mardelle
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-22 23:45 UTC by Alan Hagge
Modified: 2017-02-05 17:49 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
snd.noise: low_hanging+


Attachments
Example of garbled text in highlighted area of text box (9.90 KB, image/png)
2016-03-22 23:46 UTC, Alan Hagge
Details
Comparison of text border in 0.9.10 (top) vs 16.04 beta (bottom) (43.78 KB, image/png)
2016-03-22 23:47 UTC, Alan Hagge
Details
attachment-8134-0.html (1.46 KB, text/html)
2017-02-05 17:49 UTC, Alan Hagge
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alan Hagge 2016-03-22 23:45:50 UTC
When editing existing text in a title clip, I'm running into various issues that I wasn't seeing in 0.9.10.  Here are the issues (all seen using kdenlive version 4:16.07.70+git20160321.1e66f4b5-0ubuntu0~sunab~wily1).  Hopefully it's enough detail to reproduce locally:

- Clicking one time in a text area doesn't put the focus into the text area (or put up an editing cursor).  If you double-click in the text area, it highlights the word that the cursor is on, so that any typing erases the word and replaces it with what's typed.  It makes it virtually impossible to insert text into an existing text area.  What I'd expect is that a single-click would select the text box, a double-click would put the text cursor at the location of the arrow cursor, allowing me to type at that point into the text, and a triple-click would highlight the word under the cursor.

- Sometimes (but not always), when I double-click into an existing text area and start typing, the screen ends up with a garbled text area - the text that I type ends up as a set of thick vertical lines in the highlighted area of the text box.  But once the screen refreshes, the text seems to be as expected.  See attachment for an example.

- The vertical cursor that indicates where text will be inserted is often not visible when I'm in "insert text" mode.  If I type, characters will appear, but often not where I expect them.  The cursor needs to be more visible, and needs to be in an outline format in case the I'm working on top of black background.

- The dashed line text box border seems to be much less visible on the 16.04 beta release than it was with 0.9.10.  In fact, at times only part of the border is visible (see attached screenshot showing a 0.9.10 text box above a 16.04 text box).  In addition, clicking on the various text box positioning icons not only moves the text box, but changes which borders are visible.

- The lack of an "undo" capability often leads to frustration, as I will click once in a text area and hit the [Backspace] key, expecting the cursor to move back one space.  Instead the entire text box is deleted, with no way to recover it.

I realize that some of these issues existed in the 0.9.10 version, but I'm hoping that they can be cleaned up for the 16.04 release.

Thanks for anything you can do!
Comment 1 Alan Hagge 2016-03-22 23:46:41 UTC
Created attachment 98036 [details]
Example of garbled text in highlighted area of text box
Comment 2 Alan Hagge 2016-03-22 23:47:31 UTC
Created attachment 98037 [details]
Comparison of text border in 0.9.10 (top) vs 16.04 beta (bottom)
Comment 3 Wegwerf 2017-02-05 11:12:40 UTC
Bug reports are intended to give devs a quick and concise description of a singld bug, with instructions or an example project to reproduce them quickly. I understand that you took a lot of your valuable time to file this very detailed report. Unfortunately, as time already told, it cannot be handled by the devs. Reasons are that the report crams multiple different bugs into a single report, which is a nightmare to tackle. Even the report title is a clear no-go sign, as it is totally unspecific. Some of your issues have been fixed, as far as I remember. Feel free to report individual concise reports focusing on a reproducible bug only each one.
Comment 4 farid 2017-02-05 11:51:35 UTC
Note that I've linked a phabricator feature to this bug report: https://phabricator.kde.org/T3020 

Since it is closed I will copy the suggestions there. 

Thanks Alan for the contribution and feel free to participate at the phabricator link.
Comment 5 Alan Hagge 2017-02-05 17:49:18 UTC
Created attachment 103850 [details]
attachment-8134-0.html

Thank you for the feedback.  I can state at in the intervening months since
this bug was first reported, most, if not all, of the issues reported
therein have been addressed.  Now the titling subsystem is once again the
simple-to-use system that I enjoyed using in the 0.9.10 release.

Thanks for the devoted work on this wonderful editing system!

On Sun, Feb 5, 2017 at 3:51 AM, farid <bugzilla_noreply@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=360877
>
> --- Comment #4 from farid <snd.noise@gmail.com> ---
> Note that I've linked a phabricator feature to this bug report:
> https://phabricator.kde.org/T3020
>
> Since it is closed I will copy the suggestions there.
>
> Thanks Alan for the contribution and feel free to participate at the
> phabricator link.
>
> --
> You are receiving this mail because:
> You reported the bug.
>