06-07-2016, 04:10 PM
I was not able to reproduce the problems.
I tried with slightly modifying the PowerToys\EventManagerDragSample sample that comes with Ab3d.DXEngine and the click events are always triggered there.
I assume that you are using EventManager3D to get click events.
I would advice you to check the following:
1) Check that you set CustomEventsSourceElement property on EventManager3D to a DXViewportView or even better a parent Border - that element must have Background set (it can be Transparent but should not be null). Thous this is probably not a problem, because you get some events.
2) Do you change the model significantly after the first click? It is ok to just change the material, but if you change the Model3D or MeshGeometry3D, then the next click might be still registered to the old Model3D - in this case check why the click works again when the mouse is moved.
3) Comment registering events with EventManager3D and manually subscribe to MouseDown and MouseUp on the CustomEventsSourceElement. In the MouseUp call your code that is called in Click event. See if you get both events. If not, try to find out why WPF would not trigger those events.
4) You might try to set the UsePreviewEvents property on EventManager3D to true - this will subscribe to Preview... events instead of standard events.
If none of this will help, I would ask you to prepare a simple sample application that can be used to reproduce the problem. Then send me the sample with feedback form (http://www.ab4d.com/Feedback.aspx)
I tried with slightly modifying the PowerToys\EventManagerDragSample sample that comes with Ab3d.DXEngine and the click events are always triggered there.
I assume that you are using EventManager3D to get click events.
I would advice you to check the following:
1) Check that you set CustomEventsSourceElement property on EventManager3D to a DXViewportView or even better a parent Border - that element must have Background set (it can be Transparent but should not be null). Thous this is probably not a problem, because you get some events.
2) Do you change the model significantly after the first click? It is ok to just change the material, but if you change the Model3D or MeshGeometry3D, then the next click might be still registered to the old Model3D - in this case check why the click works again when the mouse is moved.
3) Comment registering events with EventManager3D and manually subscribe to MouseDown and MouseUp on the CustomEventsSourceElement. In the MouseUp call your code that is called in Click event. See if you get both events. If not, try to find out why WPF would not trigger those events.
4) You might try to set the UsePreviewEvents property on EventManager3D to true - this will subscribe to Preview... events instead of standard events.
If none of this will help, I would ask you to prepare a simple sample application that can be used to reproduce the problem. Then send me the sample with feedback form (http://www.ab4d.com/Feedback.aspx)
Andrej Benedik