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 34157 - I18N - Some parts of popdown windows do not fully appear in other local
Summary: I18N - Some parts of popdown windows do not fully appear in other local
Status: VERIFIED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: Explorer (show other bugs)
Version: 3.x
Hardware: Sun Solaris
: P2 blocker (vote)
Assignee: _ tboudreau
URL:
Keywords: I18N
: 34103 (view as bug list)
Depends on:
Blocks: 33246
  Show dependency tree
 
Reported: 2003-06-04 16:28 UTC by Unknown
Modified: 2008-12-23 12:56 UTC (History)
1 user (show)

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 Unknown 2003-06-04 16:28:22 UTC
Description: 
Using pseudo localized product, with each message or label
having additional multibyte text, and using -fontsize 16
option, running in Chinese locale,

File ->New -> Expand J2EE-> Session Bean EJB ->
 Click Next ->EnterEJB Name,
Click Finish ->The Session Bean is created in the explorerwindow 
->Right click and choose Properties from the context menu -
>Click the Properties tab ->Click on Component Interface it is observed t
hatthe suffix doesn't appear in the drop down menu items.
see attached image --

This is also observed on few properties in "References" and "Sun ONE
 AS" tab, namely "Resource Env Reference mapping" etc.

This occurs also in applicable properties in creation of any kind of EJB beans
or Applications.


Assumption is that user should be able to see
all items in a given window when it appears and should
not need to resize it to see those things.

That is, the UI area or window should dynamically resize
itself to show the needed contents.
(this does not apply to contents of textfields, areas
controlled by scrollbars or vertical resizing controls
like in options window)

To emulate in non multibyte locale without multibyte
in messages or longer messages, you may need to run
with fontsize 18 or 20 to see what we are seeing with
fontsize 16.

Can team also review resizing and fontsizing approach
in general for other parts of modules ?
Docs and others have requested that for
3.5.X and Nevada that no fixes involve actual changing
of UI like adding, modifying or deleting a message or UI
component as part of fixing these issues.

This issue is marked with the FONTSIZE keywork; bugs so
marked will not appear on quality dashboards and will not
need to be waived or fixed for English FCS products of this
release.


A comment.
Comment 1 pzajac 2003-06-05 08:27:20 UTC
reassigned to propertysheet
Comment 2 _ tboudreau 2003-06-06 11:20:47 UTC
Probably this could be solved by the property sheet basing
its preferred size on the default font size.

Question:  How often is a user likely to use the context
menu to show a static property sheet for something, instead
of using the embedded property sheet in the main window?

If this is not a common action, I would prefer to leave
this issue - the entire property sheet is due to be 
replaced within a couple weeks, and any further maintenance
of the old codebase is not time well spent.

BTW, if this is also a problem for the property sheet in
the main window, please file against the window system 
subcomponent - that's what handles the default layout of
the main window.
Comment 3 _ tboudreau 2003-06-11 02:21:43 UTC
This can't be fixed terribly well, since the property sheet
does not contain anything until after it's shown - its
preferred size at the time the window system is sizing it
is 0,0.

I've removed all of the hardcoded setPreferredSize() calls
in the codepath (PropertySheetView, NbSheet), with the 
exception of the call in PropertySheet itself (otherwise
you get only a titlebar).

I've increased the default size to 280x280 and overridden
getPreferredSize to check the size of a default font from
UIManager, and adjust the return value based on a factor
of its relationship to the default font size for no 
localization (11).

The alternative is to call setPreferredSize whenever the
tab is changed, which would result in a UI bug being filed
because the property sheet window size is changing when
you switch tabs, and we'd just end up rolling it back.

Checking in core/src/org/netbeans/core/NbSheet.java;
/cvs/core/src/org/netbeans/core/NbSheet.java,v  <--  NbSheet.java
new revision: 1.3; previous revision: 1.2
done
Processing log script arguments...
More commits to come...
Checking in
openide/src/org/openide/explorer/propertysheet/PropertySheet.java;
/cvs/openide/src/org/openide/explorer/propertysheet/PropertySheet.java,v
 <--  Propert
ySheet.java
new revision: 1.110; previous revision: 1.109
done
Checking in
openide/src/org/openide/explorer/propertysheet/PropertySheetView.java;
/cvs/openide/src/org/openide/explorer/propertysheet/PropertySheetView.java,v
 <--  Pro
pertySheetView.java
new revision: 1.11; previous revision: 1.10
done
Processing log script arguments...
Mailing the commit message to cvs@core.netbeans.org,
cvs@openide.netbeans.org (from tb
oudreau@netbeans.org)
Comment 4 _ tboudreau 2003-06-11 15:35:02 UTC
*** Issue 34103 has been marked as a duplicate of this issue. ***
Comment 5 David Simonek 2003-06-13 14:29:04 UTC
Reviewed, OK, but watch for the screen size should be done using
Utilities.getUsableScreenBounds.
Comment 6 _ tboudreau 2003-06-17 01:33:19 UTC
Merged to release35.  Fix for NbSheet in trunk can be found
in NbNodeOperation which was recently refactored.
Comment 7 naveen 2003-07-03 05:31:47 UTC
Build : 0625 Zh ML Build
JDK :1.4.1_02
OS :Win2k Zh Loclae

Verified the fix using above configuration,hence marking the bug as
fix.

thanks
Naveen