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

Tymond <tamtamy.tym...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REPORTED                    |NEEDSINFO
                 CC|                            |tamtamy.tym...@gmail.com
         Resolution|---                         |WAITINGFORINFO

--- Comment #1 from Tymond <tamtamy.tym...@gmail.com> ---
Ad 1.: it's to make sure we can talk to the person back, and that we don't get
too much spam. Also it's KDE-wide, not something Krita team has a huge
influence over. There are other places people can complain about Krita (reddit,
KDE forum, krita-artists.org) and we're fine with writing bug reports based on
their experiences, if there is a bug to fix. It's even better, actually, in
case someone is to make a bug report for the first time: for example, you
mentioned a few issues in one bug reports, while every issue should have their
own bug report (2a, 2b and 2c could be together, but 2d is very different) for
developers to have easier time to fix them. (And sometimes issues reported by
users fits the user support forum better).

The text tool is kind of still very rough and we know about it. There is a lot
of work that needs to be done to get it right, because Qt, which is the library
Krita uses, is too limited to allow for what we want to achieve and what users
would want out of the text tool. Now the paid Krita team members are working on
resource management system rewrite so we don't have time to focus on the text
tool as well, and text tool and shortcuts system are two other big issues we
need to fix in the future.

Ad 2a, 2b and 2c: you know you (for now) need to select the text, then change
the values. Then you need to click "Apply" or "Save" to see the effect on the
canvas. Yes, it's tedious, I agree.

Ad 2a: reproducible; although the last used fonts are on top of the list.

Ad 2b: reproducible

Ad 2c: reproducible, it's because it takes the current Foreground color for the
font.

Ad 2d: I cannot reproduce it. What exact steps do you make to get the text on
the canvas? Even with default settings (on, let's say, a new canvas using the
"Texture 256x256" size template), you should get the Lorem ipsum text on the
canvas just by activating the text tool (if your current Foreground color is
different from the canvas color enough for you to see it...).

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to