iraf.net

Hi Peter,> One other respectful suggestion: I use the "Flip X" and "Flip Y"
> commands a few times a year. On the other hand, I use
> "Register" a hundred times a day, and "Match LUT" a couple times
> a day. If I had my druthers, there would be Register and Match LUT
> buttons at the top of the window, in place of the Flip X and Flip Y
> buttons, or maybe alongside if you weren't too worried about the
> available blank space.
It occurred to me you could do this as a keystroke command using the
X translations resource. For instance, edit your .Xdefaults file to
include:XImtool*imagewin.translations: \
!Ctrl <Key>r: call(cpRegisterFrames) \n\
!Ctrl <Key>m: call(cpMatchFrames) \n\
!Ctrl <Key>f: call(nextFrame,$name) \n\
!Ctrl <Key>b: call(prevFrame,$name) \n\
<Btn1Down>: call(makeMarker,$name,$x,$y) m_create() \n\
!Shift <Btn2Down>: crosshair(on) \n\
!Shift <Btn2Motion>: crosshair(on) \n\
<Btn2Up>: crosshair(off) \n\
<Btn2Down>: call(zoom,$x,$y) \n\
<Btn3Down>: call(windowColormap,$x,$y) \n\
<Btn3Motion>: call(windowColormap,$x,$y) \n\
<EnterWindow>: enter-window() \n\
<LeaveWindow>: leave-window() \n\
<KeyPress>: graphics-input() \n\
<Motion>: track-cursor() call(wcsUpdate,$x,$y)Then either restart your X session or reload the resources using % xrdb -load ~/.XdefaultsOnce done a Ctrl-r will register the frames, a Ctrl-m will Match LUT. I
don't think you can just add the new translations with a #override or
#augment directive since the translation table is replaced when the GUI is
loaded, so you have to specify the whole thing. Similarly other functions
can be mapped to keystrokes in the same way, just ask.Cheers,
-Mike