Outrageously poor performance on Win11 especially Recipe Load/Save buttons

[PLCHorse]

Is there any way I can improve the Recipe Load and Save performance on a windows 11 pc? I installed advancedHMI on a number of machines with a rather sizeable recipe - but the windows 11 mini PC's I used - advancedHMI is brought down to its knees when I hit either recipe load or save... I'm talking 3 to 5 minutes each time. I have to imagine something is bad wrong... I also noticed the application itself is not too "snappy" in general on these machines, which are running nothing else besides AHMI and are brand spankin' new... I didn't think AHMI was all too resource intensive. The responsiveness I believe is tolerable but the Recipe Save and load is atrocious!

[Archie]

Check the Task Manager to see how much CPU and memory AdvancedHMI uses. Generally .NET applications are very lightweight and efficient since they are compiled. I have not run anything on Win11, so I have not experience with it yet.

[PLCHorse]

Ok there were 8 copies of AHMI running on the poor computer and this was taking 75%+ CPU... which on a weak machine was crippling.

One copy of AHMI is a much more reasonable 4% at idle and 20% during recipe save which is now taking 20s - tolerable.

The application wasn't actually "open" though, so it isn't closing cleanly... hence the poor performance.

So actually the issue is you close AHMI and it doesn't actually close.

I think I had the limitation removed on AHMI for having multiple open at the same time and I should put that back, but ultimately the not closing cleanly will still be an issue in the future. Is there a seperate thread about the application not closing?

[PLCHorse]

I think I found the problem..... ME!

"The design of the FormChangeButton is to always use them to navigate between the forms and make all the forms borderless so they cannot be closed.

There are multiple ways around this if you want your secondary forms to have a sizable border with a close button (X). One is to not use the FormChangeButton, but to use a standard windows button and in the click event, just show the second form without hiding the first form.

The other is to put a handler for the FormClosing event on the second form, and in that code, show the MainForm.
"

[Archie]

The MainMenuDesign pattern takes care of this. It is a form that stay open all the time. When it is closed, it closes everything.

[PLCHorse]

How do I add a form control so that MainPage / MainMenu.VB shows when I close any other form?

I tried to set ControlBox to False- but actually on windows 11 - the control box is there - drawn by windows itself! (thanks, microsof)

[Archie]

The MainMenu pattern is described here:

https://www.advancedhmi.com/forum/index.php?topic=1549

It docks a menu of form change buttons on one of the screen edges. It is also good for things that you want to always have running such as data logging or barcode scanning.

[PLCHorse]

This helps a lot. I'm a lot closer. Thank you Archie.

I Have a lot of screens already done "the old way" and I don't want to change them, so my approach to this is the Main Menu is simply going to be a "goto main" and an "exit" button - and nothing other than that.

The exit button does nothing however. I looked at the code, theres nothing inside
    Private Sub ExitButton_Click(sender As Object, e As EventArgs) Handles Button1.Click

    End Sub

[Archie]

There is a decent example project showing the MainMenu structure:

https://sourceforge.net/projects/advancedhmi/files/advancedhmi/3.5/SampleProjects/

LargePressHMIonPanelPC