DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18503>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18503 Resizing issues Summary: Resizing issues Product: JMeter Version: Nightly (Please specify date) Platform: All OS/Version: All Status: NEW Severity: Normal Priority: Other Component: Main AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] JMeter's resizing behavior isn't ideal. In particular, if your JMeter window is large, and then you switch to a new component, then make the window smaller, the component will not resize. Instead, scrollbars will appear and the component will remain the same size. The cause of this behavior is in the MainFrame class. When a new component is selected, it will set the component's preferred size to the current available space. Since the component is inside a scrollpane, this means that the component will never resize below this currently available space, resulting in the behavior described above. The fix for this in MainFrame is quite simple. But unfortunately, many of the JMeter components rely on this behavior to get a reasonable initial size. So several other components need to be updated when this change is made. The patch I'm attaching includes the MainFrame fix as well as adjustments to several other components which obviously needed it. I took a quick look at each of the components and I think I caught all of the key ones, but I can't promise that all of the components will start with a reasonable size and resize properly after this fix. If you find a component that is not correct, please let me know and I'll work on it. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
