home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!ursa!buzz
- From: buzz@fsrg.bear.com (Buzz Moschetti)
- Newsgroups: comp.windows.open-look
- Subject: Re: DevGuide3 / XView3 bug?
- Message-ID: <BUZZ.92Aug27210519@fsrg.bear.com>
- Date: 28 Aug 92 01:05:19 GMT
- References: <1992Aug27.202151.15060@ariel.ec.usf.edu>
- Sender: news@ursa.UUCP
- Organization: Bear, Stearns & Co. Inc.
- Lines: 12
- In-reply-to: gohel@sunburn.ec.usf.edu.'s message of 27 Aug 92 20:21:51 GMT
-
- In article <1992Aug27.202151.15060@ariel.ec.usf.edu> gohel@sunburn.ec.usf.edu. (Himanshu Gohel (CS)) writes:
- [...deleted...]
- Digging around a bit, I found that the .G file and the _ui.c
- file both had the correct sizes that I specified. I played
- around a bit and found that once dg3 generated code so that
- instead of explicit sizes, it used XV_EXTEND_TO_EDGE instead.
- But that didn't seem to change anything.
-
- If you grab a sizing "handle" on a Devguide panel and over-extend the
- banding box *beyond* the borders of the parent (command) frame, then
- the size as stored in the .G file (and consequently generated in the .c
- file by gxv) will be XV_EXTEND_TO_EDGE.
-