Community
Participate
Working Groups
When a section is expanded on the query page and the size of the dialog is not sufficient to show all controls without a scroll bar the dialog should be resized so that entire page is visible without a scroll bar.
Frank, before we start working on this let's look at generalizing the query page.
(In reply to comment #1) > Frank, before we start working on this let's look at generalizing the query > page. QK, but I first finish my work for bug# 168204 ([patch] support bugzilla's usermatchmode for matching names to email addresses).
Created attachment 191056 [details] patch V1 committed patch
Created attachment 191057 [details] mylyn/context/zip
Steffen, if you do not want the change for SearchPage please reopen this bug.
Please revert the change to SectionComposite. We need to come up with a better strategy that only packs or resizes the dialog when it is necessary.
Please also remove this chunk of code in the BugzillaSearchPage: Display.getDefault().asyncExec(new Runnable() { public void run() { scrolledComposite.reflow(true); scrolledComposite.getShell().pack(true); } }); I am not sure that pack is the right strategy at all since it can actually shrink the dialog which we should never do.
patch V1 is now reverted! (In reply to comment #7) > > I am not sure that pack is the right strategy at all since it can actually > shrink the dialog which we should never do. I use pack() because I found this in TaskUIPreferencePage.createAdvancedSection in expansionStateChanged Thoughts for how to solve this without pack()?
Created attachment 191580 [details] patch V2 Here the next version (now in HEAD) Steffen, please verify!
Created attachment 191581 [details] mylyn/context/zip
Created attachment 193201 [details] small fix
This looks pretty good to me. Frank, could you take a look at Window.getConstrainedShellBounds()? My sense is that we should pass the new size through that method to make sure the window never exceeds monitor bounds.
(In reply to comment #12) > This looks pretty good to me. Frank, could you take a look at > Window.getConstrainedShellBounds()? My sense is that we should pass the new size > through that method to make sure the window never exceeds monitor bounds. Window.getConstrainedShellBounds() is protected and we need a way to access this from SectionComposite. Thoughts?
Args, that's unfortunate. We may need to create a copy of that method in a utility class in the commons then.
Created attachment 195023 [details] patch V3 (In reply to comment #14) > Args, that's unfortunate. We may need to create a copy of that method in a > utility class in the commons then. Class org.eclipse.mylyn.internal.commons.ui.WindowUtil hold the need method.
Created attachment 195024 [details] mylyn/context/zip
patch V3 is now in HEAD.