Hi, I strong believe thar PostMessage solves the request: "update gui, outside main thread" Native handles, like Windows Handle, is hidden from the user perspective. Therefore using in Windows driver and not using in GTK, IOS and Android drivers, will not disturb users. In your example, You use a button widget, but can receive and process all messages is the Window Handler inside "Ihandle the_dialog." In this way, add one field to store native handler, in user_data structure and use only with Windows Functions API formal proposal.
Users do not will ask if IUP_PostMessage is implemented in different ways in Windows, GTK, IOS or Android. Running... Touching Windows Event Loop will add one branch and one function call, in every message received by app, slowing down more and more. Summing up: All drivers are free to implement in your own way, and from the users perspective, no matter how it was solved. Using Native Handler (windows), inside API, hidden from the user, works. PostMessage solves the problem, without add any cost and slowing event loop. Attempts to confuse the discussion, with evasive allegations, as users doubts, they do not help! Best regards, Ranier Vilela ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Iup-users mailing list Iup-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/iup-users
