spacetelescope / stginga

Ginga products specific to STScI data analysis.
https://stginga.readthedocs.io
BSD 3-Clause "New" or "Revised" License
6 stars 10 forks source link

cannot interact with box: always panning #48

Closed stscieisenhamer closed 9 years ago

stscieisenhamer commented 9 years ago

In MultiImage, MIPick, or Pick, the box cannot be interacted with. The main image is always in pan mode. The one way I have found is to hit the 'd' key. This should bring up the distribution algorithm choosing, but instead allows moving and editing of the box.

It doesn't matter what mode is chosen: move, draw, or edit.

Notes

stscieisenhamer commented 9 years ago

@ejeschke Heads up. However, I have just upgraded to OS X 10.10, and am looking to see if some default with the trackpad has changed.

stscieisenhamer commented 9 years ago

OK, this makes absolutely no sense: So, I had run our stginga script a number of times, always with the above issue.

Then, just for kicks, I ran ginga expecting the same result. But, to much amazement, it operated normally; I was not perpetually stuck in pan mode. This is baffling because stginga is just a wrapper around ginga.

Well, then I run stginga. Lo and behold, all now works normally!?!?!?!

WAT

ejeschke commented 9 years ago

@stscieisenhamer, can you try a couple of things? 1) try pressing Command with the cursor explicitly focused in the window (if you are using a Mac, Control otherwise) when it appears stuck in Pan mode? Also 2) try the Escape key. Let me know your findings.

ejeschke commented 9 years ago

I've noticed that sometimes on Linux, if you press Control in the window, but then navigate away from the window before releasing, Ginga does not get the event notification of Control key going up. I've never seen this on a Mac, but it may be possible.

stscieisenhamer commented 9 years ago

@ejeschke I had tried Escape and other modifier/key/click combos, all to no avail.

I suspect, due to the events of stginga not working->ginga working->stginga working, that somehow there was another cached pyc issue.

If it occurs again, I'll at least be prepared to track down.