Created attachment 117296 [details] Before and after clicking on button Show View 3D Graph SUMMARY The windows "KStars FITS Viewer" and "Sky Chart" are enlarged by a factor of 3-4 STEPS TO REPRODUCE 1. Start KStars 3.0, open the profile Simulator, record a Preview in the Imager pane 2. In the "KStars FITS Viewer", click on Show View 3D Graph and select a star 3. OBSERVED RESULT The size of the two windows "KStars FITS Viewer" and the Sky Chart is enlarged by a factor of 3-4 and it is impossible to set them back to their normal size. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: MacOS: Mojave 10.14.2 Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION This happens ONLY on my MacBook Pro , NOT on my iMac ! iMac Retina 5K, 27", late 2014, 24GB RAM, Mojave MacBook Pro Retina, 15”, Mid 2014, 16GB RAM, Intel i7, Mojave
This is really a weird bug and I tried all weekend to find a solution. On my MacBook Pro (Retina display), I re-installed KStars v. 3.0, the system (macOS Mojave 10.14.2), and I logged under another user : to no avail. Because the bug doesn't occur on my iMac (also Retina display), I transferred the app KStars, the folders kstars and the preferences from my iMac to my MacBook Pro : to no avail. I changed the display resolution : to no avail. Don't know what to think.
The bug is linked to KStars 3.0.0 running under macOS Mojave ! Here is another test on an erased SSD : 1/ Clean install of macOS High Sierra : no bug with KStars 2.9.8 and KStars 3.0.0 2/ Clean install of macOS Mojave : no bug with KStars 2.9.8, but bug with KStars 3.0.0 3/ The results are the same whatever to which computer I attach the SSD.
I would appreciate to know if another user is having the same bug . Very simple to test under macOS Mojave : - run KStars 3.0.0 with the profile "Simulators" - capture a preview and click on the button "Show View 3D Graph" to select a star - are the two windows "KStars FITS Viewer" and the Sky Chart enlarged ?
Hi Jean Claude, I think this bug was a QT bug, but I think it has since been fixed. It was definitely weird, Thanks, Rob