This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 8213 - Window positioning and dialog painting all messed up in remote X session
Summary: Window positioning and dialog painting all messed up in remote X session
Status: CLOSED INVALID
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 3.x
Hardware: PC Linux
: P1 blocker (vote)
Assignee: issues@platform
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2000-11-06 18:02 UTC by ibrandt
Modified: 2008-12-23 11:12 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ibrandt 2000-11-06 18:02:02 UTC
I have Forte IE Beta2 installed on a Solaris7/Sparc server w/ Sun jdk1.3FCS, and
am running it from a RedHat7/Intel X/Gnome/Sawfish session w/ Sun JDK1.3FCS.
There are many errors with window positioning and dialog painting.  When
starting Forte the splash screen will draw itself in seemingly random locations
on the screen.  Then the main window will draw itself mostly off the top of the
desktop, making it impossible to drag it back vi the titlebar.  Other widows,
dialogs, and menus all exhibit strange poistioning behavior.  Most property
editors and save dialogs etc will also only draw about 3/4 of the content pane
as in this sketch...

____________
|       |   |
|   A   |   |
|       |   |
---------   |
|    B      |
-------------

Zone A will be painted correctly, zone B will be an empty gray zone.  These
zones persists in relative scale if the window is draged into smaller or larger
sizes.

I'm submitting this one as a blocker because it is making Forte unusable in a
multiuser setup.  If I install forte locally on the RedHat Client there are no
issues with painting or positioning.

Thanks,

Ian
Comment 1 Jesse Glick 2000-11-06 20:25:59 UTC
Sorry, but I have to reject this bug. You say that everything is OK if you use a
local X connection. If that is so, it is not a Forte bug, since from a Java API
perspective remote vs. local X status is completely invisible. So it is very
likely a bug in the JDK. Are you sure you have all recommended Solaris patches?
People do sometimes run the IDE over a remote X connection, and while it is not
as fast, it does work (I do it every day in fact). This sounds like a low-level
display problem in the JRE native code, maybe.
Comment 2 ibrandt 2000-11-06 22:32:59 UTC
Okay,

Makes sense.  I am sure I have all the recommended patches (or superceding
patches) for JDK1.3 installed.  I'll take this to Sun.  Thanks.
Comment 3 pzajac 2002-09-11 09:38:27 UTC
verified
Comment 4 Quality Engineering 2003-07-01 16:20:37 UTC
Resolved for 3.4.x or earlier, no new info since then -> closing.