|
Gianluca Administrator Posts: 1274
04/10/2023
|
I don't like at all the perspective of having two different branches so I created a beta version (8.00.8677) with a new option to choose how the OS resizes syMenu.
Normally the resizing is the one we learnt could have some graphical issues but, going to Options - General, you can choose to go back to the virtual resizing. In this case the graphical result is not so clear, the fonts are quite blurred and the lines are not so sharp, but you are sure Windows does a perfect job and every command is perfectly visible.
I hope this can help to overcome every doubt that could prevent a user from updating to the new 8.
|
|
|
link
|
|
scentse Posts: 27
04/10/2023
|
Gianluca wrote:
Well if the situation is as you describe, SyMenu is not alone in this mess. I hope MS can fix this behaviour soon because I can do nothing.
I knew this wasn't entirely accurate...
Unaware how much code you had to write, but I agree your solution is far more elegant.
The "virtual resizing" toggle improves many of the graphical glitches. (text isn't blurry at all. Just a little soft)
- icons now match hitbox size
- most text fields are no longer cutoff'
- structure menu in options is displaying correctly
- window title bars are no longer cutoff
Other non-critical glitches remain
- checkboxes still overlay their corresponding text
- top category/sort row is still cutoff in Item Manager
- Virustotal/License Information is still cutoff in Item Manager
However... the text for the toggle itself is cutoff. So if a user doesn't know what they're looking at, it's unlikely that they would enable it.
Would it be possible to somehow incorporate the "Virtual Resizing" toggle into the initial configuration and/or post-upgrade experience?
Furthermore, enabling the toggle requires the program be restarted. Can that be automated? Or is an informative popup preferable?
e.g. "the program needs to be restarted for this to take effect".
That said - With this option, I would have zero apprehension about upgrading to 8.
edited by scentse on 04/10/2023
|
|
|
link
|
|
Gianluca Administrator Posts: 1274
04/10/2023
|
My hope is that virtual resizing will soon be useless because Windows will start to do its job better and better. So I would not include the option in the initial wizard.
Plus, at the initial wizard you still don't know if you need the option or not. The glitches start to appear when you load the most complex forms not in the wizard.
Again... the virtual rendering shouldn't have any problem because Windows renders the forms with default DPI (96) in a sort of sandbox, then it zooms the image for the user screen (this is the reason for the blurring)... so where do those glitches come from???? Probably it's again the bad GPU management that Windows does in the sandbox phase too...
Well I never saw such a large unreliability from Windows.. What were they thinking about when they implemented it?
Anyway I'm happy to hear that the new option can be decisive for the 8 adoption.
|
|
|
+1
link
|
|
scentse Posts: 27
13/10/2023
|
HUGE IMPROVEMENT on this new build!!!!!!!
(2023.10.13 - v.8.00.8686)
Zero glitches on the virtual resizing.
With the regular DPI scaling:
ITEM MANAGER
>Any critical UI elements which were previously invisible are now visible (i.e. "Apply All", checkboxes next to Status column)
>Grid/Table is displaying properly, even when resizing.
>Free Space bar graph is displaying correctly.
>Certain elements remain small, but functional:
- Titlebar (titlebar element itself?, as the text remains large but x/- buttons are small)
- Icons, but their hitboxes now match the icon size.
- SyMenu/Nirsoft Suite tabs
- Search field
- Program information text is small (exception are the hyperlinks and VirusTotal icons) - **this is an improvement**
CONFIGURATION
>Tree is displaying correctly.
>Checkboxes are displaying correctly.
>Many elements remain small, but functional
>Save and Exit button has text cutoff
OPTIONS
>Checkboxes are displaying correctly.
>Most corresponding text fields are displaying properly
>Some corresponding text fields are cutoff.
Regular DPI Scaling Screenshot
Virtual Resizing Screenshot
edited by scentse on 13/10/2023
|
|
|
link
|
|
Gianluca Administrator Posts: 1274
13/10/2023
|
There's a reason for this: I found a machine with the graphical issues you reported and I've been able to fix them one by one.
Anyway I don't completely agree with you because some objects are still broken (for example the font inside textbox and listbox doesn't scale correctly yet and remains too small) but we are on the right path now.
Thank you for your help, it was fundamental.
|
|
|
+1
link
|
|
scentse Posts: 27
08/11/2023
|
THANKS
2023.11.08 - v.8.00.8712 (.NET Core 8)
Wow. Looks Great. Nearly there.
Initially I didn't see any changes. The sizing was identical to the previous beta.
Seems due to SyMenuConfig.zip
When using the Config from the previous beta, several elements continue to display incorrectly.
Deletion of the config, prompts the creation wizard for a new one upon the next launch.
The newly created Config functions as intended, with elements displaying correctly.
Fortunately it appears SyMenuItem.zip can be carried over just fine.
Item Manager
- Title Bar text remains cutoff
- Icons & hit-boxes remain small
Configuration
- Save & Exit text is cutoff
SyMenu Options
General
- Text-entry field is cutoff on bottom edge.
Menu
- Text-entry fields are cutoff on bottom edge.
- Tooltip Selection entry is outside the visible window
Theme
- Text-entry fields are cutoff on the right edge
- "Show-shadow" text is cutoff
- Checkbox entry is outside the visible window at bottom of list
- The preview graphic is displaying elements incorrectly
ALL
- The x & - buttons in the title bars for all Windows remain small.
|
|
|
link
|
|
scentse Posts: 27
18/11/2023
|
Several of the UI elements reverted back after a few days.
Deleting SyMenuConfig.zip, relaunching, & running the wizard temporary resolves it.
But once the program is closed & restarted, the UI elements revert back to displaying incorrectly.
I copied a "clean" SyMenuConfig.zip before closing the program.
I then readded the "clean" Config back before relaunching.
But the problem remains.
Either some setting isn't being properly retained/respected or something is being rewritten on program launch.
Unaware of dependencies, but the only a few things change in the config .xml.
1. startMenuLocations add in host and x,y coordinates.
2. icons are populated
https://i.imgur.com/uA2gCnw.jpeg
|
|
|
link
|
|
Gianluca Administrator Posts: 1274
19/11/2023
|
Well I'm working on the glitches but finally there is some good news: the .NET Core 8 has been released so the SyMenu version I've just published is built on a final (LTS) framework. This means I finally
have a stable platform to work with.
I imagine a lot of the glitches you are experiencing have not been fixed by a simple framework change but at least from now on every fix I'll do will be stably fixed.
IMHO the only option stored in the SyMenuConfig.zip that can change something with visualization is the <system ... DPIUnware="False" /> that corresponds to the checkbox "Check this for issues on HD monitors" in Options - General. Every other element doesn't impact the form visualization. The change you've experienced is probably originating from some other reasons.
|
|
|
+2
link
|