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: | Show full/Resize connection error message on New Connection Wizard | ||
---|---|---|---|
Product: | platform | Reporter: | azizur <azizur> |
Component: | Dialogs&Wizards | Assignee: | Stanislav Aubrecht <saubrecht> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | mmirilovic |
Priority: | P3 | ||
Version: | 7.0 | ||
Hardware: | PC | ||
OS: | Windows 7 x64 | ||
Issue Type: | ENHANCEMENT | Exception Reporter: | |
Attachments: |
001.png - the window at normal size
002.png - when er-sized horizontally 003.png - how it should be.... proposed patch v1 |
Created attachment 108168 [details]
002.png - when er-sized horizontally
Created attachment 108169 [details]
003.png - how it should be....
It's been a month now. Would anyone give an update on this? Confirmed on Product Version: NetBeans IDE 7.0.1 (Build 201107282000) Java: 1.7.0; Java HotSpot(TM) 64-Bit Server VM 21.0-b17 System: Windows 7 version 6.1 running on amd64; Cp1252; de_DE (nb) It also applies for Derby. I assume it's independent from the DB driver but an issue of the diplaying dialog. Proposed solution: replace the JLabel (I assume!) with a scrollable and possible resizable text field displaying the error. I'll look on it. The mentioned problem roots in the wizard descriptor. A message of a wizard could always be longer than one line, so there needs to be a way to display the complete message. I'll attach a patch that adds a button with an ellipsis symbol to the errorpanel. When that button is clicked a notification with the whole message is generated. Created attachment 123568 [details]
proposed patch v1
The full error/warning is available in a tooltip, isn't that enough? I'm afraid but I don't think that the tooltip is enough. If I see such a dialog, it's pure luck if I try the tooltip approach. Ideally the errormessage can even be copied to the clipboard (Just in case when I want to copy the message and send it to s.o. else). From UEX point of view having a lengthy message cropped in dialog and having it accessible only through tooltip is not satisfactory. Even the solution with a button that would open an error panel is not optimal. Do I understand it right that the message is not generated inside NB and that that is the reason why there is problem to break it into several lines ? But even if NB infrastructure generally does not do this automatically, I hope it should be possible to intercept the message string in this particular case and to insert linebreaks into it so that it gets displayed in full in ordinarily sized dialog.. It is not a problem to wrap error messages. The problem is that it would mean that either scrollbars would show in the wizard window or the whole wizard window would need resize with every message change. I don't think that either solution is acceptable. But the connection dialog window can implement its own error messaging... The text in error/info message is selectable with mouse so Ctrl+C copies the text to system clipboard. I've also added popup menu with 'Copy to Clipboard' item. core-main a33d1685be85 |
Created attachment 108167 [details] 001.png - the window at normal size The connection error message on New Connection Wizard for mySQL (Connector/J driver) Dialogue Window is not readable. How to re-produce? 1) Open Services Panel (Ctrl+5) 2) expand Databases list -> Drivers 3) right-click MySQL (Connector/J driver) and select "Connect Using..." and you'll be presented with New Connection Wizard for mySQL (Connector/J driver) Dialogue Window 4) fill in the details with some database server details that does not work 5) Press "Test COnnection" button and wait 6) You should get error message saying cannot establish connection .... Now the error message is so long it's not possible to read the entire message. You can resize the Dialogue Window vertically but still not readable. If you resize horizontally and its readable on large (17inch) monitor. See attached images for details.