I'm a DevOps minimalist. I work on projects that web interfaces, desktop interfaces, run as services, access MSSQL, access DBFs, work with COM objects, host ActiveX controls, are the ActiveX control, are the COM object, and I maintain the build process for the projects.
These days I write as much C# code as I do VFP code, and some VBScripting for the build server.
I finally got FoxUnit setup and working with one of my projects. I should have started TDD years ago.
Lessons are a reminder that we are always needing to be taught something so we may teach others.
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Stephen Russell Sent: Friday, December 04, 2020 4:19 PM To: profoxtech@leafe.com Subject: Re: MDI window theme github issue
It has been decades since I have done forms-based apps. Now it seems to be API and or workflows in a variety of different host systems.
On Thu, Dec 3, 2020 at 1:34 PM Tracy Pearson tracy@powerchurch.com wrote:
The file picker has never been an Child window in a Multi Document Interface (MDI) So, some of the old look has been addressed.
The child windows in .NET Core WinForms MDI still have the old Windows 7 border. This is because the problem is in the Windows code.
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Stephen Russell Sent: Thursday, December 03, 2020 1:02 PM To: profoxtech@leafe.com Subject: Re: MDI window theme github issue
.NET 5 addressed this issue and brings modern visuals into a Win Forms app. That file picker looked like it was from Win95 days. It is supposed to now pull in the current version of Windows going forward. This was
per
Marcus Edger in a Code magazine video on .NET 5 about 2 weeks ago.
On Thu, Dec 3, 2020 at 10:51 AM Tracy Pearson tracy@powerchurch.com wrote:
Hello everyone,
My coworker found this and shared it with me today. I have tested to see VFP apps correctly show the MDI form with a theme
in
Windows Server 2012. If you have a github account and would like to vote this up. I say thank you!
https://github.com/dotnet/winforms/issues/3691
It's not just a Winforms issue, it's a Windows base code issue. I hope it gets fixed.
Have a good one! Tracy
[excessive quoting removed by server]