{"push_id":3121328837,"size":1,"distinct_size":1,"ref":"refs/heads/apiProposal","head":"023a36763da3d17ea6c8631839f592dd76f51bbd","before":"175fb31fde48fa33ab20a57a094ea38e2682a74c","commits":[{"sha":"023a36763da3d17ea6c8631839f592dd76f51bbd","author":{"name":"kpreisser","email":"20fde4e3a1b5b6f3832b469f4108f89305784c94@users.noreply.github.com"},"message":"Remove the \"ResultCommonButton\", \"ResultCustomButton\" and \"ResultRadioButton\" properties from TaskDialog.\nIn order to correctly handle the resulting button, we need to cache the button instance and its original button ID when the callback handler for the ButtonClicked notification returns true, because that is likely the button ID returned by TaskDialogIndirect. This can be a button that is no longer part of the TaskDialog because it already navigated, so we cannot simply search for the returned ID in the button collections.\nAlso, when that handler returns and there were radio buttons in the GUI state from which the ButtonClicked handler was called, the TaskDialog seems to return the ID of the last radio button that was selected before navigation. As it is complex to do that correctly, we simply don't retrieve the resulting radio button ID, as the user can check which radio button was selected by checking the \"Checked\" property.","distinct":true,"url":"https://api.github.com/repos/kpreisser/TaskDialog/commits/023a36763da3d17ea6c8631839f592dd76f51bbd"}]}
{"actor":{"display_login":"kpreisser"}}