Search Results

Hi, I am seeing a similar issue as first reported here - Dropdown widget listbox closeup question If an edit widget is under the dropdown's listbox when clicked the edit box also receives a WM_NOTIFICATION_RELEASED message. The edit widget currently uses this message to do some other action. I can work around the issue by using the WM_NOTIFICATION_CLICKED message rather than WM_NOTIFICATION_RELEASED but that is not the behaviour I would like. Is this a limitation you are aware of? I see this beh…

Thanks for the reply, still struggling to get your driver working however. See my code below. I have tested that I am getting valid data back from the touch controller, stepping through the assembly it appears to never call GUI_TOUCH_StoreStateEx. As another test I wrote a new driver and called GUI_TOUCH_StoreStateEx myself, this is actually working ok. Cheers Source Code (63 lines)

Do you have any example of using the GUITDRV_ADS7846 touchscreen driver? The info in the manual is a bit lacking, an example of the GUITDRV_ADS7846_CONFIG pfSendCmd and pfGetResult callbacks would be very helpful. Regards

Have not got time to test, but a version diff suggests the file has not changed.

I am using STM32CubeF4 (v1.5.0) - st.com/web/en/catalog/tools/PF259243

I was seeing exactly the same behaviour, receiving no WM_NOTIFICATION_RELEASED events when WM_MakeModal was being used. All was ok when testing under the simulator. I am using STemwin and traced the issue down to ST's not so good touch driver. You call BSP_TS_GetState to read the touch driver info, however x and y info is only written if a touch is detected. The ST code was actually using x and y even if the data was not valid. C Source Code (5 lines) My solution was to make sure the parameter w…

C Source Code (3 lines) Thanks.

Hi, I have an application that uses multiple language support, however I have noticed an issue with strings ending in certain chars are not correctly handled. C Source Code (54 lines) In the below example if i select a string I do not get the correct string returned, because some of the strings in strings_french are ending in 'é'. C Source Code (2 lines) infact returns "charge sélectionné/disponible:", rather than the correct "charge disponible". I have found two workarounds: 1. remove any 'é' a…

Hi, I am a dev on the openocd project. you released a while back the above document, it seems to have vanished from the jlink download section. The new article is still available however: segger.com/pub/PR/pr_segger_jlink_usbprotocol.pdf Any ideas why? I have the released version just wondering whether it has been updated since then. Cheers Spen