Printable View
Hi all,
Editor Screen Display: I am running Windows 10 on a Lenovo laptop with the screen display resolution set to 1366 x 768. When I launch the latest version of the Kasina Editor the Editor screen is cropped at the bottom (see snip).Attachment 964
The same problem occurs whichever page I display. I don't seem to be able to move or resize the screen to access the hidden buttons. Has anybody else had this issue? If so, I would be grateful for any advice.
Tim
The actual window size is 1024 x 768. You must have your Display zoom set to 150% or larger. Go to Control Panel > Appearance and Personalisation > Display > Make text and other items larger or smaller. Tell me what the setting is there.
Sorry to say Windows 10 Display Management does not work that way.
According to Windows 10 forums, quite a few people are having Display Management problems following upgrade to Windows 10, including (as is the case with me) Brightness Control is locked on Max and no longer adjustable via Function and Arrow Keys.
I have logged this as an issue on the Lenovo Forum and will let you know the outcome. It is possible that I will have to uninstall Windows 10 and revert to my old OS, Windows 7.
Hi Tim,
There is display scaling in Windows 10. Right click on your desktop and choose Display Settings. From the window that pops up check your settings outlined in red.
Attachment 965
I have the opposite problem on my Lenova Yoga 2 with a high dpi display. The window is too small. I have researched today and think I know a way to fix it. I will update this thread when I have something working.
Best,
Scott
Hi Scott,
Ya, I checked display scaling when it first happened. It was 100% then. Just re-tried. See first clip on the attachment. Setting is definitely 100%. I have tried altering resolutions too but all I end up with is the same cropped screen, only smaller and less well-defined.
So I tried the Windows 10 Compatibility Troubleshooter. See second and third clips. After the TS did its thing, I tested the Kasina Editor again. Still cropping the critical bottom portion of the screen. Looks and smells like a Windows 10 problem to me.
BTW, I have OTHER Windows 10 issues. My keyboard brightness control doesn't work now. The screen is set on full brightness and can't be dimmed by either the Lenovo keyboard or Windows 10 slide controls. That's a major problem for me because I have light sensitivity since my cataract operation. My Outlook and Excel programs in Office 2003 have major bugs for which the only fix is (guess what?) a paid upgrade. And what's more, since I have had Windows 10 more than a month, it is impossible to revert to Windows 7. I would have to re-load all my non-MS apps from source. Not possible.
I certainly don't recommend an upgrade to Windows 10 to anybody unless they have tech staff, time and money to sort out the consequences.
Hope your research is moreproductive than mine.
Best
Tim
Try this build and see if the issue improves: https://github.com/scottosx/KasinaBa...ases/tag/1.5.3
Note this is a pre-release in testing so others can safely ignore.
Scott,
Reporting back. Downloaded and tried the pre-release. No, 1.5.3 does not improve the screen cropping issue.
Tim
Hi Tim,
As a test would you try to increase the font size with the slider mentioned above. Your window is obviously being scaled by some setting. As mentioned the actual editor window size is 1024x768. Maybe increasing the font size will trigger my HDPI code (or maybe not it is what we are testing)
Thanks,
Scott
I've been working with this more.
In a Windows 10 virtual machine with the resolution set to 1368x768 (closest I can get) at 100% display scaling the window is fine. At 125% I am experiencing the problem you are having.
Attachment 967
Attachment 968
So, somewhere (maybe the graphics card properties?) then screen is being scaled.
Still, my code needs to handle this better. I will continue to work on it.
Scott, I'm making some progress at last following your penultimate suggestion. Not a perfect outcome but an workable one. I need to re-work and re-prove the processes and will also take into account your last comment. Once I am confident I have the best possible interim solution sans any code update by you I will get back to you with the steps and the screen clips. Later today probably.
OK Scott, latest update. The combination of 1.5.3 plus increasing the font size with the slider seems to have tweaked the graphic card properties. Previously the display scaling showed 100% at all times irrespective of where the slide was positioned. Now I can move the slide between 100% and 125%. At 125% with resolution set at the "Recommended" 1366 x 768, my Desktop icons and apps displays are all OK, as per my pre-Windows 10 environment. But the Kasina Editor screen is cropped as previously shown, so you were correct in your initial assessment that the display was actually set at 125% notwithstanding that the Window 10 slider control said 100%.
The work-around is to re-set display scaling to 100% before opening the Kasina. The Editor then opens showing the full screen as per attached clip. BTW, the Maximise Button on the Kasina Editor isn't operating - I guess you probably knew that - it's not a Windows 10-related issue. When I have finished using the Kasina Editor I re-set scaling back to 125% so I can read my icons and use my other apps.
The work-around is perfectly acceptable pending a code review so no need to give this a high priority.
Thanks for your help.
Best
Tim
It is good that you are getting the same results of what I can reproduce in the virtual machine. That makes it much easier to find a resolution. I have some more leads on fixes.
What I am hoping to avoid because it is a massive amount of code is to numerically scale and position GUI elements. The development environment I use will soon release an auto layout functionality (they already have it for iOS). So, doing it manually (well actually by calculation) would soon be obsolete.
Great. No worries about waiting for auto layout functionality. At least you have a heads-up on Windows 10 incompatibilities.
Thanks again.