Bug 438835 - "Fit to page" and "Fit to width" functions appear to work relative to original workspace despite being in "Canvas-only mode"
Summary: "Fit to page" and "Fit to width" functions appear to work relative to origina...
Status: RESOLVED WORKSFORME
Alias: None
Product: krita
Classification: Applications
Component: General (show other bugs)
Version: 4.4.5
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-06-17 23:32 UTC by haglunddalton
Modified: 2021-06-19 13:50 UTC (History)
1 user (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description haglunddalton 2021-06-17 23:32:50 UTC 
SUMMARY
 When using "fit to page/width" while in "Canvas-only mode" fits the canvas where it used to be in the standard window.

STEPS TO REPRODUCE
1. Zoom, rotate, or pan the canvas
2. Activate "Canvas-only mode" with the "tab" key
3. Activate "fit to page" with the "2" key, or "fit to width" with the "3" key

OBSERVED RESULT
 Canvas is panned and zoomed in where the canvas window was originally located.

EXPECTED RESULT
 Canvas should be panned and zoomed relative to the window while "Canvas-only mode" is active.

SOFTWARE/OS VERSIONS
Windows: 10

ADDITIONAL INFORMATION
 - Canvas size was 1920 X 1080px 300dpi
 - Fresh install of Krita
Comment 1 Alvin Wong 2021-06-19 09:15:31 UTC 
Cannot reproduce on both 4.4.5 and master (Windows)...
Comment 2 haglunddalton 2021-06-19 10:31:21 UTC 
After further examination (and random tests), was no longer able to reproduce the bug after other unrelated applications were removed. Suspect odd interaction in startup application or virus. Unable to determine which specific application might have caused the interaction.

Thank you, and I apologize.
Comment 3 Alvin Wong 2021-06-19 13:50:11 UTC 
It's okay. I guess we will never know what really happened. Closing as resolved.

If you see it happen again and found out what actions might have triggered it, feel free to reopen.