yufan@cs.keele.ac.uk (Yufan Hu) (04/16/91)
Hi, I have a problem when using -iconic option. I want to start a application with -iconic set. The application will create more windows by itself and all these subsequent winodows should not start up in iconic form. But cuurently them do. I tried to create ApplicationWindow and call ApplicationWindow->iconic(false) before mapping it. But seems not effect. Could somebody help me to solve this problem? =========================================================================== || JANET : yufan@uk.ac.keele.cs || Yufan Hu, || || BITNET: yufan%cs.kl.ac.uk@ukacrl || Department of Computer Science, || || other : yufan@cs.keele.ac.uk || University of Keele, Keele, || || UUCP : ...!ukc!kl-cs!yufan || Staffordshire. ST5 5BG. U.K. || ===========================================================================
linton@marktwain.rad.sgi.com (Mark Linton) (04/17/91)
In article <7649.9104151912@lulu.cs.keele.ac.uk>, yufan@cs.keele.ac.uk (Yufan Hu) writes: |> Hi, |> |> I have a problem when using -iconic option. |> |> I want to start a application with -iconic set. The application will create |> more windows by itself and all these subsequent winodows should not start |> up in iconic form. But cuurently them do. I tried to create ApplicationWindow |> and call ApplicationWindow->iconic(false) before mapping it. But seems not |> effect. |> |> Could somebody help me to solve this problem? |> I just put in a change for 3.0-beta that will make -iconic et al. only be interpreted for ApplicationWindows. If you are using interactors, you can also workaround this by defining a name for your toplevel interactor and define the resource "*name*iconic:off".