(1) There are few controls, and it is difficult to use and the appearance is very so. The most exuberable thing is the Toolbar control: (1) The designer thinks that you use the icon to all buttons, or use the text tag, otherwise it is the brain into the water; (2) If you try to place other controls on Toolbar (eg If you are following yourself; (3) The most couldn't be used by IF ... Else statement, which button is clicked, my god! It is no wonder that the control of Windows Forms has been written on the Internet.
(2) The metric unit uses a pixel, and it is very troublesome to do a resolution. Only coordinates (inches, millimeters, etc.)-independent of Microsoft began in Avalon.
(3) The package of Win32 is too high and incomplete, resulting in many cases to be handled. The Windows Forms control or application that can be found online does not contain similar [DLLIMPORT ("User32.dll")].
(4) Asynchronous calls are difficult to use: There are many other parts that need to be transferred to the callback in the .NET Framework, which generally allows simultaneous incoming status values to facilitate use in callbacks, such as ThreadPool.QueueUserWorkItem (waitcallback callback, object state, And Control.invoke is to make you frustrated, if you use the MethodInvoker delegate or EventHandler to delegate yourself to pack status values (because they do not receive status values), otherwise you have to define a callback delegation. Oh, my, god! If there is no C # 2.0 anonymous method, I really don't know how much this SHIT code will be written.
(5) List view Sort: .NET Framework set class sort is incoming ICOMPARER interface control sort (for example, arraylist.sort (iComparer)) in the sort method, and the author of ListView is very unsolicited, you will give the iComparer interface to ListViewItemsorter. Attribute, then call without any parameter SORT method. I don't understand what is the special benefit of such inconsistency.
(6) Strue ...
