https://bugs.kde.org/show_bug.cgi?id=523751
Bug ID: 523751
Summary: Reference images positions are not perceived by the
canvas edges until one of the shapes is moved
Classification: Applications
Product: krita
Version First 5.3.3
Reported In:
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severity: minor
Priority: NOR
Component: Tools/Reference Images
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
DESCRIPTION
Whenever a .kra file is opened, the canvas won't immediately perceive the
reference images position to change how far you can pan the canvas around, you
have to move one of the reference images first, then the canvas will update how
far away from the image you can pan, no longer tied to the boundary of the
image
STEPS TO REPRODUCE
1. Add a reference image outside the image
2. Save the .kra file
3. Reopen the .kra file
4. Try the pan tool to move to where the reference image is
5. Move the reference image any amount to any direction
6. Try the pan tool again
OBSERVED RESULT
You can't pan beyond the image boundaries without moving a reference image
first.
Video of the observed result: https://youtu.be/FASSMUmhaeY
EXPECTED RESULT
You should be able to pan as far as the reference image boundary is without the
need to move a reference image beforehand. This behavior can be observed from
any Version prior to 5.3.0 (e.g. 5.2.16).
Video of the expected result: https://youtu.be/u-kIGBDxkFg
SOFTWARE/OS VERSIONS
Operating System (available in the Info Center app, or by running `kinfo` in a
terminal window):
Build ABI: x86_64-little_endian-lp64
Build CPU: x86_64
CPU: x86_64
Kernel Type: linux
Kernel Version: 7.0.11-arch1-1
Pretty Productname: Arch Linux
Product Type: arch
Product Version: unknown
Desktop: KDE
Appimage build: Yes
KDE Plasma Version: 6.6.5
KDE Frameworks Version: 6.26.0
Qt Version: 6.11.1
ADDITIONAL INFORMATION
This bug can be traced all the way back to 5.3.0, any version prior to 5.3.0
(e.g. 5.2.16) does not have this bug.
This bug is also present in all of the 6.x.x versions.
I did not test whether this was fixed in any of the git master or nightly
builds.
--
You are receiving this mail because:
You are watching all bug changes.
