Hi,
The offset menu problem has been fixed in v4a (and v3). If you are still
seeing it with v4a, please let me know what window manager you are using.
Juergen Kreileder, one of the Blackdown porters, has done lots of testing
on this issue (and other awt related issues with window managers) and here
is what he posted to the porting list recently:
>I'm aware of that problem (although I can't reproduce it with NetBeans
>but with appletviewer using v4a/v5 and lesstif).
>
>Here's the latest report on window managers:
> kwm, icewm, fvwm2, fvwm2-plus: OK
>
> scwm, fvwm95: frame changes location after unmap/remap
> (setResizable())
>
> fvwm: frame changes location after unmap/remap
> some problem with repeatedly pressing the 'move +1+1' button
> in the noresize example from bug #144
>
> ctwm: the offset problem with appletviewer
> changing the menu bar breaks the window's layout temporarily
>
> wmaker: the offset problem with appletviewer
> changing the menu bar increases the frame's height by 1
>
> olwm, olvwm: changing the menu bar breaks the window's layout
> and can result in a segmentation violation
Are you by any chance using WindowMaker? Please let me know which window
manager shows the offset menu problem, and we will try to fix it in our
next release.
The sheer number of window managers and the fact that they are all not of
equal quality or perform ops in the same way, results in lots of problems
under awt.
Kevin
----------------------------------------------------------
Kevin B. Hendricks
Associate Professor, Operations & Information Technology
School of Business, College of William & Mary
Williamsburg, VA 23187, [EMAIL PROTECTED]
http://business.tyler.wm.edu
