Even with the code exactly the same as the Win32 one that still happens, and for unknown misterious reasons if the control is on a form instead of a Group Box it works normally.3 - A third problem found while investigating the other ones is that the difference between the windows client are and the client area that LCL expects was being ignored under Windows CE.That indicates that there was a problem with TWSWin CECustom Check Box. Even with the code exactly equal to the win32 interface the width was still too small, so an extra 10 pixels factor was added arbitrarely to fix that until a better solution is found - Fixed 2 - Aditionally TCustom Check Box descendents inside a TGroup Box (but not on a form) paint a white background instead of painting the correct background color.The way to handle background color changing on a series of controls is by handling the WM_CTLCOLORSTATIC message.Currently there are some small issues which sometimes with nested pack records compiler does not generate the required code. But note that using packed records will influence speed a lot as all of its members are treated as unaligned. The Windows CE interface will try to automatically detect the kind of device which is being run if nothing is specifyed by the user. Currently it should work just like on win32, althougth maybe the Left/Top position should always be ignored, because a Handheld may have a small screen.It's also necessary to check if all border styles are supported (how could one resize a form on a handhelp?The SPARC and some implementations of the ARM (*) don't support this and raise a bus error if you read data like this.(*) there are extensions to the ARM core which can handle it, but this Depends on what functionality the manufacturer of a specific core has Implemented. 16-bit and 32-bit values need to be 4-byte aligned in memory. Or use newly added "unaligned" keyword before using them.
Since you have a 8bit bus, you are able to address all individual bytes, so reading is not a problem.Now imagine a CPU with a 32bit data bus and reading a byte.Data is read in chunks of 32bits (=4 bytes) and it is addressed by multiples of 4.Predicting that some people will desire to have the X button, it was provided a switch to control the title buttons policy.There are some values possible: Screenshots This is a title with "X" minimize button: This is a title with "OK" close button: Implementation details The "OK" button will send a WM_COMMAND message, which is handled on wincecallback.inc, with w ID=IDOK.