Welcome to iraf.net Wednesday, April 24 2024 @ 06:53 PM GMT
pskoda |
01/12/2010 12:59PM (Read 2603 times)
|
|
|
Status: offline
Registered: 12/20/2005
Posts: 23
|
Hi Mike,during testing of my interactive previewer I have faced strange problem with persistency of xgterm window. When I normaly run some graphics task for the first time the graphics window is opened at some default location with some default size. When I change the position and size (e.g. to make it long strip for spectra) of it, the further graphics obey this geometry and give output in this (moved and resized) window. But when certain tasks are run (namely [b:ee83e5a967]gkimosaic[/b:ee83e5a967] or [b:ee83e5a967]stdgraph[/b:ee83e5a967], but I have the feeling some other were doing it as well), the window size and position is reset to the default state again - which is very annoying .Is there a way how to overcome this reset ?Petr Skoda
|
|
|
|
fitz |
01/12/2010 12:59PM
|
|
|
Status: offline
Registered: 09/30/2005
Posts: 4040
|
The window size and position can be fixed using either the '*tekGeometry" X resource or by starting XGterm with something like[code:1:2d950d0fea]xgterm %640x480+200+200 -e cl[/code:1:2d950d0fea]This will create an xgterm window logged into the CL where the plot window will always be 640x480 positioned at (200,200) from the upper left of the screen.IRAF tasks have no control over window placement, however the various graphics resets and whether or not you closed a previous window may affect how your window manager places a new window if there is no resource to constrain it.-Mike
|
|
|
|
pskoda |
01/12/2010 12:59PM
|
|
|
Status: offline
Registered: 12/20/2005
Posts: 23
|
Yes, I understand the xgeometry concept, but this is not the solution I had in mind.
The nice on X is that in certain setting of given window manager you can achieve the flexible setup, when you can extend the window interactively to fit best your particular needs (taking into account the coverage of desktop by other windows or particular IRAF task - e.g. for marking arc lines I make xgterm a narrow horizontal strip over the whole bottom of the monitor, for checking of single line profiles over-plotted I make a narrow vertical strip to enlarge the depth and separation of profiles etc ...).In 99% of tasks it works and the graphics window is not reset. But I hoped to hear there is some parameter of tasks like gkimosaic or stdgraph that prevent the reset. They seem to be of a different kind than rest of IRAF graphics .
I wanted to loop over spectrum list interactively by showing a nice picture of both dispersion and spatial cuts of a line (and column) with maximal signal in one mosaic or a long merged echelle spectrum cut to several pieces one above another.The only way I have found is the gkimosaic but it resets the window size and position - which decreases its level of comfort in otherwise flexible terminal window. The xgeometry solution seems not to work as expected as only the geometry of the first - text xgterm window is controlled. But the graphics (the tektronics mode) window, which appears after e.g. implot, has still the default size and position different from the geometry parameters....
|
|
|
|
fitz |
01/12/2010 12:59PM
|
|
|
Status: offline
Registered: 09/30/2005
Posts: 4040
|
IRAF graphics are device-independent, i.e. even if you specify a 'device' with a specific resolution in the dev$graphcap file it might be scaled by the display system to a physical window size determined by the window manager or your resource settings. A VT640 has a fixed size, an XGterm can configure a window size, but an IRAF task doesn't know/care about the difference.The graphics window behavior is a function of the X11/desktop system, not the iraf task. An IRAF graphics "reset" clears the window, the representation of that window is beyond IRAF control. To the extent that an XGterm geometry resource can specify the window size you're good, but no X11 user resource or IRAF parameter/envvar can control how a specific IRAF plot is rendered. Does this answer your question?-Mike
|
|
|
|
| |
|
Content generated in: 0.22 seconds |
|