j2me移植-键值（J2ME transplantation - key）.docVIP

j2me移植-键值（J2ME transplantation - key） Transplantation of J2ME - key Canvas 1. J2ME standard API defined in the key 17 (direction, determined, #*, digital key) + 4 (key game) = 21. In general, the mobile phone, the lack of the left / right function key and C , because the three keys in the API standard is not given, so different mobile phone manufacturers for their support is also different. Mobile phone platform left function key right function key C key Nokia -6 -7 -8 Moto -21 -22 -8 SonyEricsson -6 -7 -8 Samsung -6 -7 -8 Sun Emulator -6 -7 -8 2. some mobile phone does not support RMS, such as Nokia5300 (S40 3rd FP2), Samsung mobile phone. Some 3. mobile phone if there is no signature, each IO connection requires user confirmation, such as mobile phone, SonyEricsson S40 5th, FP1. 4. some not too good to support full screen mobile phone, mobile phone such as SonyEricsson, draw in Canvas () when the coordinates are offset. The above is I want to emphasize in the development of the problem, here are some users of these problems in my development and did not encounter strong resistance, but think back may be my good luck did not encounter related problems. Come here for reference (excerpts from the original source has Wucongkaozheng). Writing is easy to transplant J2ME code When I wrote the first J2ME game, never thought of the problem of transplantation. So the game will be very difficult to transplant. Conversely, if you have planned to transplant, it is more simple. This section is that code problem. Just think, in the code between different mobile phone which will be the difference. (1) different screen sizes The main problem here is the adaptive control. Is the so-called controls, menus, text boxes, list boxes, and so on the progress of. The size of the control must be based on the screen size adaptive adjustment. According to the first said method will screen size as variables involved in the calculation of the size of the control can get the right size (adaptive