{"push_id":1356718929,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"8d5c86b97867ad20113cee36d96ce51e41be2be4","before":"cc96261d8f565339943f15f6ce83df0191c3dbdc","commits":[{"sha":"ee46f867e9bc052f38c3e51534a93aa087af9efd","author":{"name":"Joachim Pouderoux","email":"8b38f0c75b5f33c8765242de5d88d84ec7ab3d8d@kitware.com"},"message":"Fix an infinite loop that was introduced in Win32SampleMFC\n\nRecent change (MR #838) introduced an issue with MFC applications.\nThis change make vtkHandleMessage2 transfer unprocessed messages to\nthe OldProc handler. However in MFC, the window is created by MFC and\nMFC installs its event handler first. When we connect the render window\ninteractor, this one does not setup its handler on it (even if OldProc\npoints on the MFC handler). So the MFC handler catches the messages\nfirst and transfers them to the interactor through vtkHandleMessage2...\nand this one can now transfers them to the OldProc handler, which is\nthe MFC one, so it loops.\nTo fix we use the already existing feature of vtkHandleMessage2 function\nto change interactor's OldProc through a user defined message.\nWe call this function when initializing the interactor providing the\nMFC superclass event handler.","distinct":true,"url":"https://api.github.com/repos/Kitware/VTK/commits/ee46f867e9bc052f38c3e51534a93aa087af9efd"},{"sha":"8d5c86b97867ad20113cee36d96ce51e41be2be4","author":{"name":"Joachim Pouderoux","email":"8b38f0c75b5f33c8765242de5d88d84ec7ab3d8d@kitware.com"},"message":"Merge topic 'FixSampleMFC'\n\nee46f867 Fix an infinite loop that was introduced in Win32SampleMFC\n\nAcked-by: Kitware Robot <kwrobot@kitware.com>\nMerge-request: !1546","distinct":true,"url":"https://api.github.com/repos/Kitware/VTK/commits/8d5c86b97867ad20113cee36d96ce51e41be2be4"}]}
{"actor":{"display_login":"kwrobot"}}