BALL-Project
BallView bug : object at cursor is not the good one
Hi !
I'm playing with BALL and VIEW. I've discovered a bug while implementing dynamic changes on a secondary structure on click. This bug exist in BallView too. If the camera is between two secondary structures, the clic on an element (in my case a residue) will not give the element shown to the user, but the one behind the camera.
Regards,
Laura
Hi Laura,
that sounds as if the picking does not respect the near cutting plane. Does this happen in edit mode or in picking mode, and what renderer do you use (OpenGL or raytracing)?
Best,
Andreas
Am 09.07.15 um 09:37 schrieb Laura-K:
Hi !
I'm playing with BALL and VIEW. I've discovered a bug while implementing dynamic changes on a secondary structure on click. This bug exist in BallView too. If the camera is between two secondary structures, the clic on an element (in my case a residue) will not give the element shown to the user, but the one behind the camera.
Regards,
Laura
— Reply to this email directly or view it on GitHub https://github.com/BALL-Project/ball/issues/559.
Hi Andreas,
This happen in rotate/zoom mode when I double click on a Residue. Here is some screenshots I made from BALLView:
As you can see, when I'm really close to a residue, different camera positions give different names. I think this happens only when there are other residues behind (or close to) the viewport. In my own program, I use a very similar code to the Scene::showInfos() function, this explains why I see the same bug.
The problem exists in picking mode too, in yellow the selected item:
In both cases (BallView and my own program) I use the OpenGL rendering.
Best,
Laura