Xmanager Forum

framemaker window placement problematic

Last post: Thursday, December 11, 2003 7:29 PM by Hans Bouma, 4 reply

Friday, October 17, 2003 12:57 AM - Hans Bouma

framemaker window placement problematic

When using Windows as window manager, after opening more than 2 framemaker popup windows, succesively opened popupwindows appear, but are not filled where the popup overlaps the main framemaker window.
Clicking inside the popup window causes the content of the window to be drawn.

When using an xdmcp session (and therefore the remote window manager), the popup windows are placed in the background.

Friday, October 17, 2003 5:14 PM - Support

Re: framemaker window placement problematic

Unfortunately we have no answer to the problem. For further support, please provide us with the following information:

- The version of Framemaker.
- The vendor and version of the Unix server.

Thanks for your cooperation.

Technical Support
Tuesday, October 21, 2003 5:50 PM - Hans Bouma

framemaker window placement problematic


Framemaker version 5.5.6 (xm5.5.6p145)

server : HP J5000, running HP-UX 11.00
Wednesday, October 22, 2003 5:34 PM - Support

Re: framemaker window placement problematic

We were unable to get a Framemaker 5.5.6 for HP. Instead got a Linux version and it worked well with Xmanager.

Could it be possible to get an HP version of Framemaker for evaluation? There was no instruction about it in Adobe site.

Also, please check that Xmanager is the latest one. The current version is v1.3.9.8 build 9. You can find the detailed version information from "C:\Program Files\Xmanager1.3.9\Xmanager.log".

Technical Support
Thursday, December 11, 2003 7:29 PM - Hans Bouma

framemaker window placement problematic

We're using the latest version of Xmanager. I don't know about an evaluation version of Framemaker. However, I did discover the following :

The problems only occur with local window manager. In an xdmcp session the 'problemat¿' popup windows appear behind the main framemaker window. (and therefor do not need to be filled).
Therefore I assume that these windows should be placed behind the main framemaker window while using the local window manager as well.

Another surprising effect was, that when a session was started with window manager on automatic, and initially it starts using the local window manager, the local windows manager is disabled at the moment the main frame maker window appears. (leaving all the other windows unmanaged)

Apparently Framemaker wishes to manage it's own windows, and this does not work well with either the 'auto' or 'local' setting of xmanager.