home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!charon.amdahl.com!pacbell.com!sgiblab!sgigate!sgi!fido!marktwain.rad.sgi.com!linton
- From: linton@marktwain.rad.sgi.com (Mark Linton)
- Newsgroups: comp.windows.interviews
- Subject: Re: Window methods
- Date: 18 Nov 1992 19:47:30 GMT
- Organization: sgi
- Lines: 15
- Distribution: world
- Message-ID: <1ee6kiINN10b@fido.asd.sgi.com>
- References: <17463@borg.cs.unc.edu> <1e923uINNepd@fido.asd.sgi.com> <STEINARB.92Nov17092832@topas.idt.unit.no>
- Reply-To: linton@marktwain.rad.sgi.com (Mark Linton)
- NNTP-Posting-Host: marktwain.rad.sgi.com
-
- In article <STEINARB.92Nov17092832@topas.idt.unit.no>, steinarb@idt.unit.no (Steinar Bang) writes:
- |> > You need to set the appropriate attribute on the window's style,
- |> > e.g., window->style()->attribute("iconName", "foo").
- |>
- |> Won't this conflict with the resource and command line interpretation?
- |> I.e. in that setting this attribute explicitly will override any
- |> attempts to change the name at run-time, either through X resources or
- |> command line arguments.
- |>
- |> Wouldn't it be more better to set the name in the application resource
- |> default array passed to the Session constructor?
-
- Yes, defining a resource is better if the information is static.
- If the iconName is computed (e.g., argv[1]), then it has to be set
- explicitly.
-