Something else to mention. The theme border color. The below code will explain all as it's commented. I've also attached an image:- Code: Public Sub SetBorderColor(ByVal Form As Form) 'This was created as applying the raw theme accent to the border was too 'How you doin?', now it's more subtle. 'The control passed must inherit SetStyle(ControlStyles.SupportsTransparentBackColor, True) else an error will be thrown. 'Alpha can be tweaked here, or you could pass a ByVal integer 'and remove the dimensioned variable 'Alpha'. e.g. 'Public Sub SetBorderColor(Form As Form, Alpha As Integer) : End Sub Dim Alpha As Integer = 180 Dim R = SettingsThemeColor.R Dim G = SettingsThemeColor.G Dim B = SettingsThemeColor.B If SettingsApplyThemeColorToBorder = 1 Then Form.BackColor = Color.FromArgb(Alpha, R, G, B) Else Form.BackColor = Colors.ColorBorderStandard End If End Sub Usage: Code: SetBorderColor(Me) Ctor: Code: Public Sub New() InitializeComponent() SetStyle(ControlStyles.SupportsTransparentBackColor, True) End Sub Regards.
Over the next two weeks I'll be finishing up and running extensive tests on the updater. If you see there is an update available when using V2.0.0 RC2 (previous post) it should be disregarded. Although, the updater is not currently included anyhow. Unfortunately, the updater will not come with the release source code. We're very close to the V2.0.0 release, thanks everyone for helping me on this journey, it has been a good one and I've learned a lot. I'm looking forward to releasing something else soon.
I need to take another approach with my assessment ProcessWatcher. Occasionally an issue will occur in the logging which I have added in the CODE segment below. This has been a long running issue that I keep noticing, and all changes haven't helped. Code: [WINSAT]: > CPU LZW Compression 838.27 MB/s [WINSAT]: > CPU AES256 Encryption 3921.53 MB/s [WINSAT]: > CPU Vista Compression 2209.81 MB/s [ERROR]: ProcessWatcher: WinSAT was closed or unexpectedly quit '// This should not be here as the assessment was successful [XIRET]: ExitCode: 2 '// And this should be... [XIRET]: Validity Int: 1 [INFO]: Process finished '// [WINSAT]: > CPU SHA1 Hash 2156.76 MB/s [WINSAT]: > Uniproc CPU LZW Compression 165.51 MB/s [WINSAT]: > Uniproc CPU AES256 Encryption 517.93 MB/s [WINSAT]: > Uniproc CPU Vista Compression 448.20 MB/s [WINSAT]: > Uniproc CPU SHA1 Hash 564.41 MB/s [WINSAT]: > Memory Performance 25757.67 MB/s [WINSAT]: > Direct3D Batch Performance 42.00 F/s [WINSAT]: > Direct3D Alpha Blend Performance 42.00 F/s [WINSAT]: > Direct3D ALU Performance 42.00 F/s [WINSAT]: > Direct3D Texture Load Performance 42.00 F/s [WINSAT]: > Direct3D Batch Performance 42.00 F/s [WINSAT]: > Direct3D Alpha Blend Performance 42.00 F/s [WINSAT]: > Direct3D ALU Performance 42.00 F/s [WINSAT]: > Direct3D Texture Load Performance 42.00 F/s [WINSAT]: > Direct3D Geometry Performance 42.00 F/s [WINSAT]: > Direct3D Geometry Performance 42.00 F/s [WINSAT]: > Direct3D Constant Buffer Performance 42.00 F/s [WINSAT]: > Video Memory Throughput 121682.00 MB/s [WINSAT]: > Dshow Video Encode Time 0.00000 s [WINSAT]: > Dshow Video Decode Time 0.00000 s [WINSAT]: > Media Foundation Decode Time 0.00000 s [WINSAT]: > Disk Sequential 64.0 Read 466.07 MB/s 8.1 [WINSAT]: > Disk Random 16.0 Read 365.27 MB/s 8.1 [WINSAT]: > Total Run Time 00:02:40.81 [OKAY]: The assessment ran with no warnings or errors '//Here... [XIRET]: ExitCode: 0 [XIRET]: Validity Int: 1 [INFO]: Process finished Added to known issues.
1. The issue with the X buttons being off-center is still there. 2. I guess you're used to "Minimise", but AFAICT the rest of the world uses "Minimize" 3. There appears to be an issue with the notifications. Not sure how to describe it so see the attached gif. 4. Can you make the top menu bar behave like the following? a. user clicks a menu e.g. Options b. while the Options menu is open, the user hovers the Tools menu c. Options menu is closed, hover state is removed from Options and moves over to the Tools menu, and the Tools menu is opened Kinda like how a Windows app (e.g. Notepad) menu bar behaves when a menu is opened and the user hovers a different menu.
Hey @ItielMaN - thanks for testing: 1. Fixed, see the image below. Maybe me looking at the design a lot, it looks no different to me. 2. Typo corrected. 3. Fixed. I've reverted the changes to this back to RC1. I'm not keen on keeping an undocumented API in use until I'm more familar with it. 4. Yes. It's because I'm using seperate 'ContextMenu' integrations and there's no good way of tracking when one is open. Now I recreate the menu. You pointing this out just solidifies that I don't agree with the design. I may have also made a serious hiccup in Metrics. Wait on that, as we'll need to see an RC2 fix. If you see "The formal XML is missing" in 'Metrics' please let me know.
RC2-1 coming ASAP. This is mainly for the 'Metrics' and composition malfunctions, but also has a few minor enhancements. Probably tomorrow. Code: Enhancements: 1. User Interface - Off-center elements corrected (ItielMaN) - Typo(s) corrected (ItielMaN) Bugs: 1. Fixed a malfunction in 'Metrics' 2. Disabled SetWindowCompositionAttributeA() in notifications (Temporary) (ItielMaN) Would anyone like to see an option to 'manually edit' their scores in a later version?
Looks like the settings changed again in RC2. Had to click away several error messages and wipe my settings again. Fortunately, it's not much to setup, as you picked good defaults.
Yes, that will be for the custom imgur client Id. All those errors are a bit excessive, let me see if I can clean it up.
Some news: 1. I discovered and handled a new winsat error code. 2. A bug was found but only testers can have access to the information. Please send me a message. I'm working on merging the normal and verbose assessment modes. The variables will be seperated out for easier access and both forms will unify. Everything is moving forward. The updater is now finished.
Moving into the final release, I've started working with someone on design choices and wording, sometimes I can be too technical. 'Verbose' assessment has been renamed to 'In-depth' assessment and some UI elements have been shifted for ease of use. The main 'Run' assessment button is now dynamically named depending on the state of winsat. There will not be another release candidate, but testers will recieve the final code and changelog so any last minute changes can be made. This will be a private internal build so I apologise to those who have to wait, but this is a release to public so it's important for me to release smoothly. EDIT: Long time users can also test the final builds. I'll update this thread when its been passed on and/or available. However here are some changes from RC2-1 into release: Code: New: 1. Added username and system installation date (Tools > View system details) - Core.Helpers.OSHelper gained GetUsername and GetWindowsInstallDate 2. Added release id to the main form (Operating System) - Core.Helpers.OSHelper gained GetWindowsReleaseId Enhancements: 1. Ease of use UI changes 2. Screenshots now include operating system name and bitness 3. System uptime now ticks and the refresh button was removed (Tools > View system details > System uptime) Bugs: 1. Fixed program constructor pointing to static form Some changes are not listed as they only relate to internal cleanup and do not affect usage.