Dt Error

[Richard Munn]

I have a program that displays a window to an X server and calls DtWsmOccupyAllWorkspaces to force it into all workspaces under CDE. This works fine on all (non-HP) platforms except HP-UX 11.11 You get a couldn't get per screen information error if the X server is supporting PanoramiX or Xinerama.

[Alex Glennie]

So is this a SLS or multiscreen env ?

Have you made any changes to dtwm/CDE resources to reflect the multi screen env? if yes which & what?

Does this only fail at 11.11 ?

Is that the exact error.

[Steve Steel]

Hi


Do you find anything in

/var/dt/Xerrors

$HOME/.dt/*log


What does graphinfo and xdpyinfo give


Steve Steel

[Richard Munn]

OK I got this a bit wrong. I didn't really clearly define what was going where. The program is running on the X client but the X server is another platform. In fact the only Xinerama platform I have not tried is HP with SLS (since I don't have a multiheaded HP workstation). The X servers are on Tru64 UNIX, Solaris OpenVMS & Linux all of which run Xinerama, PanoramiX or some other single virutal screen extension. The same program on any of these can display to any other. I got it wrong about Xinerama anyway however, even on a single headed HP workstation the same error occurs when DtWsmOccupAllWorkstations is called.

The client shows the correct information about the X server (i.e. screen count, width, height etc.) and all windows expose correctly. It's only when the above function is called it goes wrong.

[Richard Munn]

There are no errors in any logs either on the client or X server only the message:

Error: Counldn't find per display information

which definitely comes from DtWsmOccupyAllWorkspaces.

[Richard Munn]

I have reduced my program to as simple as possible test case which demonstrates the problem.

[Rick Beldin]

I've never seen a program with DtWsm* that was written at the Xlib level. All programs that I have seen that use that function are toolkit (libXt) programs.

Quick source examination shows that there is some dependency on libXt for things like the application context and the like.

Does the sample program:

/usr/dt/share/examples/dtwsm/occupy.c

work in your environment? There's a makefile and what not in that directory as well.

[Rick Beldin]

I've never seen a program with DtWsm* that was written at the Xlib level. All programs that I have seen that use that function are toolkit (libXt) programs.

Quick source examination shows that there is some dependency on libXt for things like the application context and the like.

Does the sample program:

/usr/dt/share/examples/dtwsm/occupy.c

work in your environment? There's a makefile and what not in that directory as well.

[Richard Munn]

Thanks Rick, didn't know there was an example sitting there. Yes this one does work so I'll have to examine what is going on. On the Xlib issue, I am aware that HP-UX's DtWsm* routines depend upon the X toolkit. The reason I use Xlib is because virtually no other platform has such a dependancy. For example Tru64 UNIX is totally Xlib and it's not the only one.

It appears that DtWsmOccupy.. only works if X-toolkit is used on HP-UX which is not supposed to be the case!

[Mike Stroyan · Accepted solution]

A general dependence on XtDisplayToApplicationContext was added when CDE was made threadsafe in the 2.1 release. Any vendor moving up to CDE 2.1 would have the same requirement.