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.
Summary: | doubled scrollbars when invoking Ant Settings/Properties custom property editor | ||
---|---|---|---|
Product: | platform | Reporter: | Milos Kleint <mkleint> |
Component: | Window System | Assignee: | _ ttran <ttran> |
Status: | CLOSED FIXED | ||
Severity: | blocker | CC: | akemr, issues, mmirilovic |
Priority: | P3 | ||
Version: | 3.x | ||
Hardware: | PC | ||
OS: | Windows ME/2000 | ||
Issue Type: | DEFECT | Exception Reporter: | |
Bug Depends on: | 20570 | ||
Bug Blocks: | |||
Attachments: |
screenshot
working hack for NbPresenter.diff |
Description
Milos Kleint
2002-04-29 09:54:02 UTC
Created attachment 5585 [details]
screenshot
Looks like problem of property editor. Hmm, I didn't change scrolling in custom property editor. In NB 3.3.1 it works. CCing Properties module - does something change in properties editor?? [Milos please don't use JPEG for screenshots...GIF or PNG is non-lossy.] Trung I would guess this is a regression triggered by issue #20570. I also think it's caused by #20570, so reassigning to Trung. I'll attach patch/hack to NbPresenter which works fine for Properties custom editor. Created attachment 5601 [details]
working hack for NbPresenter.diff
Yuck, that's evil-looking. Maybe the patch for issue #20570 should just be backed out. The original problem was *not* with random special components displayed in dialogs, which generally already use JScrollPane if it makes sense. The problem was with message panes where the displayed object is a String, and a GUI component is generated for you - with no scrolling ability. However JOptionPane is used to display the messages, not NbPresenter directly. Maybe #20570 should just be WONTFIX and anyone displaying a long text message should just be responsible for reformatting it into a GUI component with a decent layout. Okay, I take a safer route. JScrollPane will be inserted in between only if the _minimumSize_ is larger than the screen not the _preferredSize_ as it is now. This is only a safeguard to make sure we don't display dialogs larger than the screen. Each dialog must still be properly designed to take the limited screen size into consideration. verified in [nb_dev](20020524) Resolved for 3.4.x or earlier, no new info since then -> closing. |