home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.sys.sun.apps:1757 comp.windows.x:15737 comp.windows.open-look:3626
- Path: sparky!uunet!sun-barr!ames!elroy.jpl.nasa.gov!sdd.hp.com!caen!uflorida!usf.edu!sunburn!gohel
- From: gohel@sunburn.ec.usf.edu. (Himanshu Gohel (CS))
- Newsgroups: comp.sys.sun.apps,alt.tookits.xview,comp.windows.x,comp.windows.x.openlook,comp.windows.open-look
- Subject: DevGuide3 / XView3 bug?
- Summary: can't generate large control areas?
- Keywords: dg3, xview3, bugs?
- Message-ID: <1992Aug27.202151.15060@ariel.ec.usf.edu>
- Date: 27 Aug 92 20:21:51 GMT
- Sender: news@ariel.ec.usf.edu (News Admin)
- Followup-To: poster
- Organization: Univ. of South Florida, College of Engineering
- Lines: 36
-
-
- Setup: Developer's Guide 3.0 (dg3); OpenWindows 3.0 (ow3);
-
- Remember that annoying bug in DevGuide1.1 that would not let you make
- windows larger than a certain size? I thought that dg3 would solve
- that problem. NOT!
-
- I have an application whose base frame is 825x700. I have two
- control areas, one going across (823x97) and another going down
- (121x600). They look great when viewed from dg3. But when I
- gxv and make the interface, both windows are cropped short -
- the first by about 50 pixels off the right, and the second by
- about 25 pixels of the bottom!
-
- 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.
-
- That leads me to believe that it's a bug in XView3, not dg3?
-
- And while we're talking about XView3 bugs, a multi-line text
- item also in the same .G file shows up without scroll bars when
- the code is generated for it! Why is that?
-
- Solutions much appreciated
-
- Thanks
-
- Himanshu
- --
- --
- Himanshu Gohel, gohel@suntan.ec.usf.edu
- University of South Florida,
- USF 3140, Tampa, FL 33620-3140
-