2,652
edits
XDSGUI: Difference between revisions
no edit summary
No edit summary |
|||
| Line 1: | Line 1: | ||
XDSgui is a GUI (graphical user interface) for XDS that is supposed to help both novice and experienced users. | XDSgui is a GUI (graphical user interface) for XDS that is supposed to help both novice and experienced users. | ||
It graphically displays the ASCII and [http://www.bernstein-plus-sons.com/software/CBF cbf] files that XDS writes, and can run useful shell commands with a simple mouse click. The design goal of the | It graphically displays the ASCII and [http://www.bernstein-plus-sons.com/software/CBF cbf] files that XDS writes, and can run useful shell commands with a simple mouse click. The design goal of the program is to enable XDS data processing without the commandline, and to supply additional graphical information, in a simple, user-modifiable and user-extensible way. | ||
program is to enable XDS data processing without the commandline, and to supply additional graphical information. | |||
The main window of XDSgui has the following sub-windows organized as tabs: | The main window of XDSgui has the following sub-windows organized as tabs: | ||
| Line 15: | Line 14: | ||
== XDS.INP == | == XDS.INP == | ||
this shows the current [[XDS.INP]] file. Coloured items correspond to the circles of the | this shows the current [[XDS.INP]] file. Coloured items correspond to the circles of the FRAME tab. Changes can be made with the simple editor, and the new version can be saved. A run of xds_par can be started (and killed). <br> | ||
The XDS.INP tab is directly connected with the | The XDS.INP tab is directly connected with the FRAME tab; changing a value in the XDS.INP tab results in immediate change in the FRAME tab. This means that e.g. an UNTRUSTED area that was positioned wrongly can be edited or simply removed in the XDS.INP tab. | ||
== Output from XDS == | == Output from XDS == | ||
| Line 59: | Line 58: | ||
== Dependencies == | == Dependencies == | ||
The program depends on the availability of [[generate_XDS.INP]], [[XDS-viewer]], and of course [[xds|xds_par]], [[xds]], [[xdsconv]], and [[xscale]]. One of the items in the | The program depends on the availability of [[generate_XDS.INP]], [[XDS-viewer]], and of course [[xds|xds_par]], [[xds]], [[xdsconv]], and [[xscale]]. The XDSSTAT tab requires [[xdsstat]]. One of the items in the TOOLS tab requires xdiff, but if that program is not available, [http://furius.ca/xxdiff xxdiff] or [http://sourceforge.net/projects/tkdiff tkdiff] may be used - please adjust the commandline below the button accordingly. | ||
== News == | == News == | ||
| Line 65: | Line 64: | ||
== Known bugs / problems / workarounds == | == Known bugs / problems / workarounds == | ||
# ''Question concerning TOOLS: "Show frame..." on Mac: it creates everything shown in the commandline but it seem to us that everything runs in the background. Therefore xds-viewer does not open anywhere as it is not seen. Also, it would be great if this image together with the predictions would be re-directed to the | # ''Question concerning TOOLS: "Show frame..." on Mac: it creates everything shown in the commandline but it seem to us that everything runs in the background. Therefore xds-viewer does not open anywhere as it is not seen. Also, it would be great if this image together with the predictions would be re-directed to the FRAME tab.'' <br> Answer: On Linux, the xds-viewer window is brought to the foreground automatically, whereas on the Mac this does not seem to happen. However, an icon for xds-viewer appears in the dock (on the right) and I can double-click it to see the xds-viewer window. I have no idea how to bring xds-viewer to the foreground automatically, and I need input from people who know Macs and tell me how to do it (on the commandline!). The reason why we do not open automatically in the FRAME tab is that one can have several xds-viewer windows open at the same time, and compare the patterns. As a '''workaround''', you can manually open the resulting temp/FRAME_$X.cbf in the FRAME tab. | ||
# ''Another question concerning TOOLS: "Further analyses" on Mac: again pointless runs nicely but there is no output for the user.'' <br> Answer: Could it be that you started xds-gui by double-clicking its icon in the Finder? In that case, there is no output visible, because there is no console. Unfortunately, for all the Tools, the output is in the console window where xds-gui was started. We will try to find out how to open a window where the output is then shown. Thus, currently the '''workaround''' for this problem is to start xds-gui in a console window. | # ''Another question concerning TOOLS: "Further analyses" on Mac: again pointless runs nicely but there is no output for the user.'' <br> Answer: Could it be that you started xds-gui by double-clicking its icon in the Finder? In that case, there is no output visible, because there is no console. Unfortunately, for all the Tools, the output is in the console window where xds-gui was started. We will try to find out how to open a window where the output is then shown. Thus, currently the '''workaround''' for this problem is to start xds-gui in a console window. | ||