From: Alan W. I. <ir...@be...> - 2002-03-01 21:52:23
|
Joao's recent xwin fix only solved a tiny part of the problem. Using ./x01c -locate -dev xwin you can click on any viewport and get back world coordinates and relative device coordinates, but as soon as you make the mistake of clicking outside a viewport, the mouse is hosed, i.e. mouseclicks are ignored from then on. Since the xwin fix, the cross-hairs turn off when the mouse is hosed, but that is the only change in the bad behaviour. With -dev tk you get identical bad results when clicking outside a viewport. However, if you stick inside viewports there is an extra twist; you get two (!) sets of coordinates for every mouse click. With -dev ntk you get identical bad results when clicking outside a viewport. However, if you stick inside viewports, you get the normal one line of results per click, but no cross-hairs are displayed at all! So there is a whole lot of little things which are not right as well as the bigger problem of the mouse stopping working entirely if you ever click outside a viewport by mistake. Once the interactive drivers, the C library and C front-end start dealing with interactive mouse clicks properly, I will want to get this working for the python (or pyqt) front end as well. I have a research project on the horizon involving the analysis of many spectra that requires good fundamental mouse interactivity for PLplot. Alan email: ir...@be... phone: 250-727-2902 FAX: 250-721-7715 snail-mail: Dr. Alan W. Irwin Department of Physics and Astronomy, University of Victoria, P.O. Box 3055, Victoria, British Columbia, Canada, V8W 3P6 __________________________ Linux-powered astrophysics __________________________ |