2008/12/26 Tamas TEVESZ <[email protected]>: > On Fri, 26 Dec 2008, Samir SAADA wrote: > > > > the capture is available at http://dawn.dev.hu/~ice/tmp/wmjava.avi > > > > > > i'm not sure whether java stuff other than those based on netbeans > > > platform exhibit this behaviour. i've seen this with at least one > > > other nb platform stuff as well. > > > > > > has anyone seen any of these before? any ideas where to start > > > attacking? > > > > This is a weird menu > > indeed. > > > I found this on the net: > > > http://karussell.wordpress.com/2008/07/26/the-most-annoying-but-strangest-bug-in-netbeans/ > > interesting. it looks like this guy too is using wmaker, and at least > one someone else also mentioned it in the comments that the bug > occurred with wmaker. > > i also found this: > http://lists.freebsd.org/pipermail/freebsd-java/2005-December/004784.html > > this exhibits the problem with wmaker. i made a little survey among > friends, and it doesn't happen with gnome or icewm; it also doesn't > happen in windows nor sco openserver 6 (neither in panorama > (essentially mwm) nor kde3), and i'm pretty sure it doesn't happen in > osx either (i have a friend who uses nb and other java stuff on osx > heavily, and i never heard him wanting to grind the tihng). thus far > i'm getting the impression that it somehow is a wmaker bug. it could > still of course be a jvm bug that somehow only manifests itself under > wmaker, but that seems quite unlikely... > > interested parties may try http://dawn.dev.hu/~ice/tmp/WelcomeApp.jar > (which is the compiled version of huang wen hui's code found above, > and probably needs jre6 to run) to see whether they can make other wms > or systems behave badly (the point is that if after a maximize > operation welcomeapp still says the same location as it did before > maximization, instead of saying -4, -4 (which seems to be the case > everywhere else, except openserver, where it's 0, 0 -- but it > shouldn't be too far off 0, 0 anywhere), then it is bad). if you can > make the above app under wmaker behave good, i'd like to hear that > too, with every possible information you can think of. > > > ./netbeans -J-Dawt.toolkit=sun.awt.motif.MToolkit > > heh, that makes my jvm (Java HotSpot(TM) 64-Bit Server VM (build > 11.0-b15, mixed mode)) segfault, albeit in native code it says... > > > I should look at dev mailing list of Netbeans, maybe they have a > > solution or other workarounds. > > the workaround is to manually move the window to the upper left corner > and only then maximize. this makes it work, but i think that in > reality it just hides the problem (the difference of the position of > the window before and after maximize is zero, so essentially the bug > remains, but transforms so that it happens to work). this method is > also harder to do on xinerama, where snapping to (physical) display > borders doesn't work (another wm bug?), so one has to be quite > precise. (maximizing in xinerama works fine, wm only maximizes a > window on the current head, not across all of them). > > i have a netbeans guy up under my sleeve somewhere, i'll try > contacting him, but i doubt this is the right direction.
well I read somewhere that this bug happened before (other versions of Netbeans with other WM) > > -- > [-] > > mkdir /nonexistent > > > -- > To unsubscribe, send mail to [email protected]. > -- To unsubscribe, send mail to [email protected].
