Bug 437770 - Cannot move layer objects with arrow keys while using Move tool
Summary: Cannot move layer objects with arrow keys while using Move tool
Status: RESOLVED NOT A BUG
Alias: None
Product: krita
Classification: Applications
Component: Tools/Move (show other bugs)
Version: 4.4.3
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-05-28 10:48 UTC by Raghavendra kamath
Modified: 2021-06-08 13:10 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Raghavendra kamath 2021-05-28 10:48:59 UTC
SUMMARY
In recent 4.4.3 appimage, 4.4.3 repository version as well as the latest nightly appimage (except flatpak nightly) moving layers objects with arrow keys across the canvas doesn't work. This to me seems like a regression

STEPS TO REPRODUCE
1. Download Krita fron the website 4.4.3 or nightly appimage
2. Create a new document and add a new empty layer, then draw some shape in it
3. Choose the move tool while the newly created layer is selected, try to move the drawn shape with arrow keys.

OBSERVED RESULT
Nothing moves

EXPECTED RESULT
It should be possible to move with arrow keys

Operating System: Fedora 34
KDE Frameworks Version: 5.82.0
Qt Version: 5.15.2
Kernel Version: 5.12.7-300.fc34.x86_64
OS Type: 64-bit
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz
Memory: 31.3 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 750 Ti/PCIe/SSE2
Comment 1 Ahab Greybeard 2021-05-29 09:00:41 UTC
I don't see that problem when using the 4.4.3 appimage and the May 28 5.0.0-prealpha (git 9db743c) appimage on Debian 10. The cursor keys work to perform a Move action in agreement with the settings in the Tool Options docker.

There is a possibly related bug report for failure of the left/right cursor keys movement with animated frames:
https://bugs.kde.org/show_bug.cgi?id=436060

SOFTWARE O/S
Krita

 Version: 5.0.0-prealpha (git 9db743c)
 Languages: en_GB, en, en, en_GB, en
 Hidpi: false

Qt

  Version (compiled): 5.12.9
  Version (loaded): 5.12.9

OS Information

  Build ABI: x86_64-little_endian-lp64
  Build CPU: x86_64
  CPU: x86_64
  Kernel Type: linux
  Kernel Version: 4.19.0-16-amd64
  Pretty Productname: Debian GNU/Linux 10 (buster)
  Product Type: debian
  Product Version: 10
  Desktop: MATE

OpenGL Info
 
  Vendor:  "NVIDIA Corporation" 
  Renderer:  "GeForce GTX 750 Ti/PCIe/SSE2" 
  Version:  "4.6.0 NVIDIA 460.73.01" 
  Shading language:  "4.60 NVIDIA" 
  Requested format:  QSurfaceFormat(version 3.0, options QFlags<QSurfaceFormat::FormatOption>(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::CompatibilityProfile) 
  Current format:    QSurfaceFormat(version 4.6, options QFlags<QSurfaceFormat::FormatOption>(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::CompatibilityProfile) 
     Version: 4.6
     Supports deprecated functions true 
     is OpenGL ES: false 

QPA OpenGL Detection Info 
  supportsDesktopGL: true 
  supportsOpenGLES: true 
  isQtPreferOpenGLES: false 

Hardware Information

  GPU Acceleration: auto
  Memory: 16039 Mb
  Number of Cores: 8
  Swap Location: /tmp
Comment 2 Raghavendra kamath 2021-06-08 13:01:36 UTC
I tested this with fedora and also with arch linux. Both the 4.4.3 appimage, repository version and latest 5.0 alpha appimages have this behaviour on both distributions. I think there is some package which is newer in these distros that is affecting the arrow keys. Do you have a live image of fedora or manjaro to test perhaps
Comment 3 Raghavendra kamath 2021-06-08 13:10:21 UTC
Aah this is just my mistake. The amount for move was 0.0001 So this bug is invalid. Sorry for wasting time.