Peter Daniel Kirchner wrote: > maybe not the simplest but start them in separate xterms with separate envs, > dx -uionly and dx -execonly, then connect them via the ui's connect dialog > specifying "connect to running server". > > Use the Image2 macro (vs Image) for interactivity. "Expand" so you can set > interactionmode to 0 for rotate interaction, for example. > > You might wish to look at > http://www.research.ibm.com/dx/docs/buildingapps/SuperviseState.html#HDR1. > 3 19 > > Per the documentation html, > http://www.research.ibm.com/dx/docs/legacyhtml/pages/refgu048.htm#HDRDISPLAY > you can specify a "where" for Display: > > where > specifies the host and window for displaying the image. On a > workstation, the format of the parameter string is: > X, display, window > where X refers to the X Window System; display is an X server name > (e.g., host:0); and window is a window name (and must not begin with two > #-characters). As a rule, it is not necessary to set this parameter. But > when it is set, the resulting Image window is not controlled by the user > interface (e.g., it has no menu options). The function of this parameter > is to specify another workstation on which to display an image (e.g., by > setting it to "X,workstationname:0, message"). Using the Image tool, you > can display the same image to another workstation simply by connecting > the module's two outputs to the two inputs of Display and setting where.
When I am using DISPLAY, I can not use hardware rendering, which is really very important in my case. Using Image2 the interaction modes aren't that good than with image 2 but at least I can use hardware rendering. Isn't there a possibility to start dx on one screen and somehow put IMAGE on the other. Another possibility I could live with would be, that I start dx on one screen and move the control panels on the other, but I think this could not be realized.. Any ideas ?? Thanks Alex
