New SyMenu releases and changelog
	SyMenu beta 8.00 
		
	
 
		
		
	
	
		| 
			
			Gianluca Administrator Posts: 1349 
			
  			
			06/03/2022
		 | 
		
			
			Hello.
  What's happening here? Why an 8 version?
 
  Well  this release is a sort of milestone for SyMenu. 
  Since the SyMenu first  version the only requirement for the host PC was to have the .NET  framework 2.0 or higher installed. This version has been heavily rewritten to  implement the new .NET 7 framework that allows to include in the SyMenu package the entire framework. This way SyMenu can be  executed with no prerequisites at all because all the needed libraries  are already included. 
  This means full portability for SyMenu.
 
  There are two cons with this approach. 1) The program size has increased a lot. This version weighs almost 70MB while the stable version weighs only 4MB. 2)  The modern .NET frameworks abandoned the support for the oldest Windows  OS (bye bye XP and Vista). The oldest supported OS is Win 7 SP1 and  SyMenu will be forced to do the same.
  PLEASE BE CAREFUL We are finally out from the alpha testing. A beta version is available since October 2022 and it means it could be used in a more extended way. Anyway I  can't assure, at this point of development, SyMenu is fully working, nor that your  configuration files will be preserved with the next version, I can't  assure the automatic update will be able to update this version in the  future... So please don't use this version as your main one. Any help  for testing will be welcome but don't do stupid things with it.
  Enjoy.
  2023.05.28 - v.8.00.8548 (.NET Core 8) 2023.06.06 - v.8.00.8557 (.NET Core 8) 2023.07.19 - v.8.00.8600 (.NET Core 8) 2023.07.21 - v.8.00.8602 (.NET Core 8) 2023.07.21 - v.8.00.8616 (.NET Core 8) 2023.08.11 - v.8.00.8623 (.NET Core 8) 2023.09.15 - v.8.00.8658 (.NET Core 8) 2023.09.15 - v.8.00.8672 (.NET Core 8) 2023.10.04 - v.8.00.8677 (.NET Core 8) 2023.10.13 - v.8.00.8686 (.NET Core 8) 2023.11.08 - v.8.00.8712 (.NET Core 8) 2023.11.08 - v.8.00.8723 (.NET Core 8) https://onedrive.live.com/download?resid=D06528ECD5C93C26%21563&authkey=!ALysxsY6dHn6988
 
 
  Here you can download a compatible version of the SyMenu plugin OpenFolder 2022.06.09 - v.0.9.0.0 https://onedrive.live.com/download?cid=D06528ECD5C93C26&resid=D06528ECD5C93C26%21214&authkey=AMg192GAC9nahjo
  edited by Gianluca on 19/11/2023
			
			
		 | 
	
	
		| 
			
		 | 
		
			
			
			
			 link
			
			
			
			
			
		 | 
	
	
		| 
			
			Gianluca Administrator Posts: 1349 
			
  			
			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
			
			
			
			
			
		 | 
	
	
		| 
			
			Gianluca Administrator Posts: 1349 
			
  			
			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
			
			
			
			
			
		 | 
	
	
		| 
			
			Gianluca Administrator Posts: 1349 
			
  			
			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
			
			
			
			
			
		 |