Bug 416894 - krita full screen in wrong monitor
Summary: krita full screen in wrong monitor
Status: RESOLVED UPSTREAM
Alias: None
Product: krita
Classification: Applications
Component: Usability (show other bugs)
Version: git master (please specify the git hash!)
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-01-29 07:50 UTC by Mobin
Modified: 2020-03-05 12:16 UTC (History)
3 users (show)

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


Attachments
attachment-22545-0.html (1.40 KB, text/html)
2020-01-29 19:25 UTC, Mobin
Details
Annotation 2020-01-31 010944.jpg (97.89 KB, image/jpeg)
2020-01-30 21:40 UTC, Mobin
Details
attachment-23902-0.html (4.78 KB, text/html)
2020-01-30 23:01 UTC, Mobin
Details
full screen bug (3.32 MB, video/mp4)
2020-03-05 12:16 UTC, Mobin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mobin 2020-01-29 07:50:04 UTC
SUMMARY
I have a setup of 2 monitors (windows extended monitor view)
krita is moved to 2nd monitor
whenever krita runs on full screen (tab on keyboard) it goes to the first monitor.
right now a workaround is to make krita NOT go fullscreen (by enabling title bar at least)

STEPS TO REPRODUCE
1. have 2 monitors on windows 10 with it set up as extended
2. run krita on main monitor
3. move it to 2nd monitor
4. tab for full screen (if you have it hid everything so it goes full screen) 
5. krita goes full screen on 1st monitor

OBSERVED RESULT
krita goes full screen on 1st monitor (as it is the main windows one)

EXPECTED RESULT
krita goes full screen on the monitor it is placed on (2nd monitor)

SOFTWARE/OS VERSIONS
Windows: win 10 x64 latest 1/29/2020 build

ADDITIONAL INFORMATION
gpu nvidia 1060 , cpu: AMD FX 8350, 16 gb of ddr3 ram
Comment 1 Rebecca Breu 2020-01-29 17:35:04 UTC
I can't reproduce it on Debian, neither with the 4.2.8 appimage nor the recent nightly appimage. Might be a Windows-specific issue?
Comment 2 Mobin 2020-01-29 19:25:58 UTC
Created attachment 125529 [details]
attachment-22545-0.html

I think it is. Might be good if we could choose a default monitor. Although
making title bar visible (preventing fullscreen) is a workaround

On Wed, Jan 29, 2020 at 9:05 PM Rebecca Breu <bugzilla_noreply@kde.org>
wrote:

> https://bugs.kde.org/show_bug.cgi?id=416894
>
> Rebecca Breu <rebecca@rbreu.de> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>                  CC|                            |rebecca@rbreu.de
>
> --- Comment #1 from Rebecca Breu <rebecca@rbreu.de> ---
> I can't reproduce it on Debian, neither with the 4.2.8 appimage nor the
> recent
> nightly appimage. Might be a Windows-specific issue?
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 3 Ahab Greybeard 2020-01-30 20:53:37 UTC
I don't have this on Windows 10 with the Jan 30th 4.3.0-prealpha (git 0657457) standalone .zip.

It goes to full screen on whatever monitor has the majority of the window on it then returns to its previous shape and size and placement.
Comment 4 Mobin 2020-01-30 21:40:29 UTC
Created attachment 125556 [details]
Annotation 2020-01-31 010944.jpg

I have it on git 1164b81
and I have this problem with dpi as well:
run on monitor one 100% and monitor 2nd has 150% scaling


On Fri, Jan 31, 2020 at 12:23 AM Ahab Greybeard <bugzilla_noreply@kde.org>
wrote:

> https://bugs.kde.org/show_bug.cgi?id=416894
>
> Ahab Greybeard <ahab.greybeard@hotmail.co.uk> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>                  CC|
> |ahab.greybeard@hotmail.co.u
>                    |                            |k
>
> --- Comment #3 from Ahab Greybeard <ahab.greybeard@hotmail.co.uk> ---
> I don't have this on Windows 10 with the Jan 30th 4.3.0-prealpha (git
> 0657457)
> standalone .zip.
>
> It goes to full screen on whatever monitor has the majority of the window
> on it
> then returns to its previous shape and size and placement.
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 5 Ahab Greybeard 2020-01-30 22:12:41 UTC
Are your monitors identical?
Are there any OS level utilities and controls whose settings could have an effect on this? (Right-click on desktop then Display Settings.)
(I rarely use Windows nowadays so I've lost familiarity with it.)

I forgot to add my system information but I don't know if it would be of any help to anyone in solving this problem:

Krita

 Version: 4.3.0-prealpha (git 0657457)
 Languages: en_US, en
 Hidpi: false

Qt

  Version (compiled): 5.12.5
  Version (loaded): 5.12.5

OS Information

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

OpenGL Info
 
  Vendor:  "NVIDIA Corporation" 
  Renderer:  "GeForce GTX 750 Ti/PCIe/SSE2" 
  Version:  "4.6.0 NVIDIA 388.13" 
  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 0, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 1, colorSpace QSurfaceFormat::sRGBColorSpace, profile  QSurfaceFormat::CompatibilityProfile) 
     Version: 4.6
     Supports deprecated functions true 
     is OpenGL ES: false 

QPA OpenGL Detection Info 
  supportsDesktopGL: true 
  supportsAngleD3D11: true 
  isQtPreferAngle: false 

Hardware Information

  GPU Acceleration: auto
  Memory: 16381 Mb
  Number of Cores: 8
  Swap Location: /tmp

Current Settings

  Current Swap Location: /tmp
  Undo Enabled: 1
  Undo Stack Limit: 20
  Use OpenGL: 1
  Use OpenGL Texture Buffer: 1
  Use AMD Vectorization Workaround: 0
  Canvas State: OPENGL_SUCCESS
  Autosave Interval: 360
  Use Backup Files: 1
  Number of Backups Kept: 1
  Backup File Suffix: ~
  Backup Location: Same Folder as the File
  Use Win8 Pointer Input: 1
  Use RightMiddleTabletButton Workaround: 0
  Levels of Detail Enabled: 1
  Use Zip64: 0


Display Information
Number of screens: 2
	Screen: 0
		Name: \\.\DISPLAY2
		Depth: 32
		Scale: 1
		Resolution in pixels: 1280x1024
		Manufacturer: 
		Model: 
		Refresh Rate: 60
	Screen: 1
		Name: \\.\DISPLAY1
		Depth: 32
		Scale: 1
		Resolution in pixels: 1280x1024
		Manufacturer: 
		Model: 
		Refresh Rate: 60
Comment 6 Mobin 2020-01-30 23:01:38 UTC
Created attachment 125560 [details]
attachment-23902-0.html

my 2nd monitor is an "xp pen artist 12" (pen display tablet) and beside
color it does not manage anything. resolution and dpi are covered by
windows. (right now on 1080p same as my main monitor but with 150% dpi -my
main is 100%-)
if I disable the dpi in krita It will fix black borders but I still have
the fullscrean problem that just only favors my main monitor not were is is
placed or have more coverage.

On Fri, Jan 31, 2020 at 1:42 AM Ahab Greybeard <bugzilla_noreply@kde.org>
wrote:

> https://bugs.kde.org/show_bug.cgi?id=416894
>
> --- Comment #5 from Ahab Greybeard <ahab.greybeard@hotmail.co.uk> ---
> Are your monitors identical?
> Are there any OS level utilities and controls whose settings could have an
> effect on this? (Right-click on desktop then Display Settings.)
> (I rarely use Windows nowadays so I've lost familiarity with it.)
>
> I forgot to add my system information but I don't know if it would be of
> any
> help to anyone in solving this problem:
>
> Krita
>
>  Version: 4.3.0-prealpha (git 0657457)
>  Languages: en_US, en
>  Hidpi: false
>
> Qt
>
>   Version (compiled): 5.12.5
>   Version (loaded): 5.12.5
>
> OS Information
>
>   Build ABI: x86_64-little_endian-llp64
>   Build CPU: x86_64
>   CPU: x86_64
>   Kernel Type: winnt
>   Kernel Version: 10.0.16299
>   Pretty Productname: Windows 10 (10.0)
>   Product Type: windows
>   Product Version: 10
>
> OpenGL Info
>
>   Vendor:  "NVIDIA Corporation"
>   Renderer:  "GeForce GTX 750 Ti/PCIe/SSE2"
>   Version:  "4.6.0 NVIDIA 388.13"
>   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 0, swapBehavior QSurfaceFormat::DoubleBuffer,
> swapInterval 1, colorSpace QSurfaceFormat::sRGBColorSpace, profile
> QSurfaceFormat::CompatibilityProfile)
>      Version: 4.6
>      Supports deprecated functions true
>      is OpenGL ES: false
>
> QPA OpenGL Detection Info
>   supportsDesktopGL: true
>   supportsAngleD3D11: true
>   isQtPreferAngle: false
>
> Hardware Information
>
>   GPU Acceleration: auto
>   Memory: 16381 Mb
>   Number of Cores: 8
>   Swap Location: /tmp
>
> Current Settings
>
>   Current Swap Location: /tmp
>   Undo Enabled: 1
>   Undo Stack Limit: 20
>   Use OpenGL: 1
>   Use OpenGL Texture Buffer: 1
>   Use AMD Vectorization Workaround: 0
>   Canvas State: OPENGL_SUCCESS
>   Autosave Interval: 360
>   Use Backup Files: 1
>   Number of Backups Kept: 1
>   Backup File Suffix: ~
>   Backup Location: Same Folder as the File
>   Use Win8 Pointer Input: 1
>   Use RightMiddleTabletButton Workaround: 0
>   Levels of Detail Enabled: 1
>   Use Zip64: 0
>
>
> Display Information
> Number of screens: 2
>         Screen: 0
>                 Name: \\.\DISPLAY2
>                 Depth: 32
>                 Scale: 1
>                 Resolution in pixels: 1280x1024
>                 Manufacturer:
>                 Model:
>                 Refresh Rate: 60
>         Screen: 1
>                 Name: \\.\DISPLAY1
>                 Depth: 32
>                 Scale: 1
>                 Resolution in pixels: 1280x1024
>                 Manufacturer:
>                 Model:
>                 Refresh Rate: 60
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 7 Halla Rempt 2020-02-17 15:11:37 UTC
Hm, if the dpi is different, then it's probably a bug in Qt. Qt 5.14, which we don't use yet, has a lot of fixes for systems where different monitors have different scaling factors. In any case, and I'm sorry I didn't see this report before, Krita doesn't have any code related to window placement. Qt handles all of that for us :-(
Comment 8 Mobin 2020-03-05 12:16:55 UTC
Created attachment 126608 [details]
full screen bug

here is a video of fullscreen bug with latest krita plus git from today.