Crazy things in interface development

Let's talk about some of my lessons.
I am involved in application development as a desktop application. ProgramFor a good user experience, many custom windows and custom controls are used in the product design. In the earliest requirement manual, the software interface needs to be implemented only by Photoshop. Everyone quickly followed the interface. But it was immediately rejected by the QA group, because XP Luna silver theme was used in both our development environment and the QA group used XP Luna blue theme and Windows 2 K, in this way, the color of some system controls on the user interface changes with theme, while some self-painted controls are still silver-gray, which is very uncoordinated. The impact of theme on the overall interface style is ignored in product design and development. We have to discuss theme support again.

In addition, a custom window requires that the scroll bar of the border be left at the left half of the screen, and the scroll bar be right at the right half of the screen. When a buddy implements it, he can judge by the half of the workingarea. workingareas is a good thing and can correctly handle the situation of taskbar on the side. Of course.CodeIt does perform well on the vast majority of machines, including QA group tests. As a result, the last beta client found a problem and the window was abnormal on his secondary monitor. Day, there is a multi-monitor this thing... The next day, the development team and the QA group added several monitors.