Compact Framework Best Practices: Creating a Graphical User Interface

I support the Windows CE application based on the .NET Framework, which has about 45 forms. There are 5 sections that lead to the desired function. The application is 100% full and it’s important that it cannot be minimized.

Since there are so many forms, it’s hard to keep track of which form should be displayed after closing. To do this, I set the property of the owner of the form before showing it, and showing the owner when it is closed.

I was also informed that it is best to instantiate all forms when the application loads, rather than deleting them to save processing time. I am not sure about that.

My question is: what is the best way to show, hide forms, where do you want each 1 form to be in front, the whole screen all the time?

+4
source share
2 answers

I would not go the way of creating 45 forms when starting the application. This will significantly reduce startup time and possibly (if not possible) run out of memory resources to provide functionality that you might not even need.

WinMo , . , , , .

, , , , (, gridview, 300 , 12). , , , , .

, "5 ", , , , () "" 5 -. , ShowDialog, 5-6 , , .Net CF (I ). , , , , , , .

z-order/task, , . ShowDialog Text ShowDialog. , Windows Mobile ( , 6) .Net( ) Running Programs, . , , Text ).

, UserControl , , . , , . Load UserControls , .

+3

, . , , , , .

- - OpenNETCF IoC framework, , , .

, :

  • ( FOrms, User CFontrols, Panels , ).
  • , "" ( , ).

- MSDN. , MVC IoC .

, - "" . , , , , , .

, , , . ARM , , , - (, ..), x86 pentium- .

, , MusiGenesis ​​, , "" . , , 47 , . , 47 . . , , , , , . ShowDialog, z- . , , .

, , - , .

+3

All Articles