[Solved] [Bug] Fullscreen issue with 'Part' containers
Forum rules
and Helpful information
and Helpful information
IMPORTANT: Please click here and read this first, before asking for help
Also, be nice to others! Read the FreeCAD code of conduct!
Also, be nice to others! Read the FreeCAD code of conduct!
Re: [Bug] Fullscreen issue with 'Part' containers
thanks a lot! I will asap the build will be available.wmayer wrote: ↑Wed Jun 05, 2019 1:46 pm See git commit 960d61254
Please check if build 16915 fixes any of your rendering problems.
Re: [Bug] Fullscreen issue with 'Part' containers
Hi, sorry for delaying in testing it...wmayer wrote: ↑Wed Jun 05, 2019 1:46 pm See git commit 960d61254
Please check if build 16915 fixes any of your rendering problems.
I can confirm the bug on FreeCAD_0.19.17072_x64_LP_12.1.2_PY3QT5-WinVS2015.7z
OS: Windows 10 (10.0)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.17072 (Git)
Build type: Release
Branch: master
Hash: 75b52c85b0b092ab79ccd26a8632a8be44c1486c
Python version: 3.6.8
Qt version: 5.12.1
Coin version: 4.0.0a
OCC version: 7.3.0
Locale: English/United States (en_US)
EDIT:
I don't know if this may help...
I noticed that this issue is present also if I UnDock the Document window, instead of calling a F11 fullscreen option.
This is related to Qt5 as you pointed out, because I don't have issue on the same release, but Qt4 based.
FreeCAD_0.19.17072_x64_LP_11.11_PY2QT4-WinVS2013.7z
-
- Veteran
- Posts: 5513
- Joined: Thu Apr 05, 2018 1:53 am
Re: [Bug] Fullscreen issue with 'Part' containers
I noticed when returning from full screen you can still hide the individual origin elements. It seems to no longer respect the origin visibility setting. This on my own debug compile using the latest source (as of yesterday) inside a virtual box ubuntu vm.
All the windows py3/qt5 builds have even more significant issues with this. The v0.18 py2/qt4 build handles it just fine except when returning from full screen the document window has to be maximized.
An alternative to full screen would be to simply hide all other panels, status bar, and menus. Then upon exiting full screen mode make all that you had to hide visible again. It wouldn't be a true full screen look -- would still have, for example, windows task bar visible -- but hopefully would not suffer the rendering issues.
All the windows py3/qt5 builds have even more significant issues with this. The v0.18 py2/qt4 build handles it just fine except when returning from full screen the document window has to be maximized.
An alternative to full screen would be to simply hide all other panels, status bar, and menus. Then upon exiting full screen mode make all that you had to hide visible again. It wouldn't be a true full screen look -- would still have, for example, windows task bar visible -- but hopefully would not suffer the rendering issues.
Re: [Bug] Fullscreen issue with 'Part' containers
Hello,
I brought my Linux to Leap 15.1 because the support for 42.3 expired.
Then I recompiled the current FreeCad version 19. Everything went well until I went into fullscreen mode with F11.
There, the view changes, the construction axbox doubles, and the construction somehow doubles.
After returning with F11 it stays that way.
I working with PartDesign.
The only remedy would be, you are currently not in the full-screen mode.
Does anyone have similar experiences?
OS: openSUSE Leap 15.1 (KDE//usr/share/xsessions/plasma5)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.17509 (Git)
Build type: Unknown
Branch: master
Hash: 9b3102a70173f0e568fc87725b58f6ea4d065a42
Python version: 3.6.5
Qt version: 5.9.7
Coin version: 3.1.3
OCC version: 6.9.1.oce-0.18
Locale: German/Germany (de_DE)
I brought my Linux to Leap 15.1 because the support for 42.3 expired.
Then I recompiled the current FreeCad version 19. Everything went well until I went into fullscreen mode with F11.
There, the view changes, the construction axbox doubles, and the construction somehow doubles.
After returning with F11 it stays that way.
I working with PartDesign.
The only remedy would be, you are currently not in the full-screen mode.
Does anyone have similar experiences?
OS: openSUSE Leap 15.1 (KDE//usr/share/xsessions/plasma5)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.17509 (Git)
Build type: Unknown
Branch: master
Hash: 9b3102a70173f0e568fc87725b58f6ea4d065a42
Python version: 3.6.5
Qt version: 5.9.7
Coin version: 3.1.3
OCC version: 6.9.1.oce-0.18
Locale: German/Germany (de_DE)
- Attachments
-
- doppelt.jpg (130.38 KiB) Viewed 1239 times
with kind regards, Berthold
Linux SuSE leap 15.5 , 64Bit
Linux SuSE leap 15.5 , 64Bit
Re: [Bug] Fullscreen issue with 'Part' containers
Can confirm with
OS: Windows 8.1
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.17505 (Git)
Build type: Release
Branch: master
Hash: 755536e9df94d2d39da1468420f1fd333c35da7a
Python version: 3.6.6
Qt version: 5.6.2
Coin version: 4.0.0a
OCC version: 7.3.0
Locale: Bulgarian/Bulgaria (bg_BG)
OS: Windows 8.1 (6.3)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.17505 (Git)
Build type: Release
Branch: master
Hash: 755536e9df94d2d39da1468420f1fd333c35da7a
Python version: 3.6.8
Qt version: 5.12.1
Coin version: 4.0.0a
OCC version: 7.3.0
Locale: Bulgarian/Bulgaria (bg_BG)
After entering fullscreen or undocking the document window all PD body visible features (currently visible feature, base planes and axes under origin, visible sketches) are displayed as copies at 0,0. If they are visible toggling visibility of the body itself hides only the geometry at bodys actual position. 0,0 visible copies stays visible unless toggled hidden. This persists only in the view (document window) that was undocker/fullscreened. If new view is created everything works fine there. In the broken view newly created bodies are properly displayed. But if the view is undocked again they too show the same error.
OS: Windows 8.1
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.17505 (Git)
Build type: Release
Branch: master
Hash: 755536e9df94d2d39da1468420f1fd333c35da7a
Python version: 3.6.6
Qt version: 5.6.2
Coin version: 4.0.0a
OCC version: 7.3.0
Locale: Bulgarian/Bulgaria (bg_BG)
OS: Windows 8.1 (6.3)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.17505 (Git)
Build type: Release
Branch: master
Hash: 755536e9df94d2d39da1468420f1fd333c35da7a
Python version: 3.6.8
Qt version: 5.12.1
Coin version: 4.0.0a
OCC version: 7.3.0
Locale: Bulgarian/Bulgaria (bg_BG)
After entering fullscreen or undocking the document window all PD body visible features (currently visible feature, base planes and axes under origin, visible sketches) are displayed as copies at 0,0. If they are visible toggling visibility of the body itself hides only the geometry at bodys actual position. 0,0 visible copies stays visible unless toggled hidden. This persists only in the view (document window) that was undocker/fullscreened. If new view is created everything works fine there. In the broken view newly created bodies are properly displayed. But if the view is undocked again they too show the same error.
Re: [Bug] Fullscreen issue with 'Part' containers
Hello,
I made two more hardcopys, here once before switching width F11 and once after. In the construction are two bodies, after switching to F11 everything is doubled and the copy is also shown twisted.
If you create a new view afterwards, then everything is ok again.
OS: openSUSE Leap 15.1 (KDE//usr/share/xsessions/plasma5)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.17509 (Git)
Build type: Unknown
Branch: master
Hash: 9b3102a70173f0e568fc87725b58f6ea4d065a42
Python version: 3.6.5
Qt version: 5.9.7
Coin version: 3.1.3
OCC version: 6.9.1.oce-0.18
Locale: German/Germany (de_DE)
I made two more hardcopys, here once before switching width F11 and once after. In the construction are two bodies, after switching to F11 everything is doubled and the copy is also shown twisted.
If you create a new view afterwards, then everything is ok again.
OS: openSUSE Leap 15.1 (KDE//usr/share/xsessions/plasma5)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.17509 (Git)
Build type: Unknown
Branch: master
Hash: 9b3102a70173f0e568fc87725b58f6ea4d065a42
Python version: 3.6.5
Qt version: 5.9.7
Coin version: 3.1.3
OCC version: 6.9.1.oce-0.18
Locale: German/Germany (de_DE)
- Attachments
-
- SchneckeRichtig.jpg (98.43 KiB) Viewed 1213 times
-
- SchneckeFalsch.jpg (166.56 KiB) Viewed 1213 times
with kind regards, Berthold
Linux SuSE leap 15.5 , 64Bit
Linux SuSE leap 15.5 , 64Bit
Re: [Bug] Fullscreen issue with 'Part' containers
Since the problem persist could you please check again in light of the last two posts?wmayer wrote: ↑Wed Jun 05, 2019 1:46 pm See git commit 960d61254
Please check if build 16915 fixes any of your rendering problems.
Re: [Bug] Fullscreen issue with 'Part' containers
A few weeks ago my actual system crashed (the HDD broke) and I switched back to my older system. On this system I can confirm that the axes and planes show up when switching to full screen mode but I don't get any other of the reported issues.
I can't remember if on the crashed computer the axes and planes showed up in full screen mode.
Since for a new 3d view we just set the scene graph without changing anything so this could be a driver bug or Coin3d has problems when the scene graph is moved to another viewer.
What happens if you create a second 3d view (see first command in View menu) instead of changing to full screen?
I can't remember if on the crashed computer the axes and planes showed up in full screen mode.
Since for a new 3d view we just set the scene graph without changing anything so this could be a driver bug or Coin3d has problems when the scene graph is moved to another viewer.
What happens if you create a second 3d view (see first command in View menu) instead of changing to full screen?
Re: [Bug] Fullscreen issue with 'Part' containers
As I already reported creating new view works as expected without duplications. Each view brakes independently from other views when undocked/fullscreened. Another thing that I just noticed - basic axes/planes stay duplicated but if a new feature/sketch is added duplication of features/sketches is fixed.
.
.