Bug 405334 - Layer Rename Text Selection
Summary: Layer Rename Text Selection
Status: RESOLVED DUPLICATE of bug 400357
Alias: None
Product: krita
Classification: Applications
Component: Usability (show other bugs)
Version: 4.1.7
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-03-11 01:44 UTC by KST
Modified: 2019-04-04 12:09 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Video (361.12 KB, video/mp4)
2019-03-11 12:02 UTC, mvowada 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description KST 2019-03-11 01:44:29 UTC 
SUMMARY
After Painting and tap f2 to rename the layer. The selection disappear and the cursor ends up behind the layer name.

STEPS TO REPRODUCE
1. Paint something
2. Press f2 to rename layer

OBSERVED RESULT
The layer name is not in selection and cursor behind layer name
https://www.youtube.com/watch?v=dMVKztYaaIU [Recording of Error]

EXPECTED RESULT
The whole layer name should be selected

Krita
  Version: 4.1.7

Qt
  Version (compiled): 5.9.3
  Version (loaded): 5.9.3

OS Information
  Build ABI: x86_64-little_endian-llp64
  Build CPU: x86_64
  CPU: x86_64
  Kernel Type: winnt
  Kernel Version: 10.0.17134
  Pretty Productname: Windows 10 (10.0)
  Product Type: windows
  Product Version: 10

OpenGL Info
  **OpenGL not initialized**
Comment 1 Halla Rempt 2019-03-11 10:20:21 UTC 
I'm sorry, but I cannot reproduce that. The layer name is selected when I press F2.
Comment 2 KST 2019-03-11 10:52:55 UTC 
(In reply to Boudewijn Rempt from comment #1)
> I'm sorry, but I cannot reproduce that. The layer name is selected when I
> press F2.

If you press F2 just after making a stroke, the layer name will not be selected. https://youtu.be/7_WR3Y5z-To
This also happens on my laptop.
Comment 3 mvowada 2019-03-11 12:02:30 UTC 
Created attachment 118714 [details]
Video

Hi. I can confirm the issue with a recent nightly (git c2fbec1) (see video).
Likely that is the same issue of Bug 400357
Comment 4 Halla Rempt 2019-04-04 12:09:42 UTC 
Yes, I think so. I've now also been able to reproduce.

*** This bug has been marked as a duplicate of bug 400357 ***