Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add/Remove references dialog box isn't wide enough #4662

Closed
daFreeMan opened this issue Dec 19, 2018 · 2 comments
Closed

Add/Remove references dialog box isn't wide enough #4662

daFreeMan opened this issue Dec 19, 2018 · 2 comments
Labels
difficulty-01-duckling Issue where no particularly involved knowledge of the internal API is needed. enhancement Feature requests, or enhancements to existing features. Ideas. Anything within the project's scope. good first issue Want to contribute? That's a good place to start! up-for-grabs Use this label in conjunction with a difficulty level label, e.g. difficulty-02-ducky user-interface This issue explicitly relates to the visible interface of Rubberduck. wpf Issue is easier to resolve with knowledge of WPF/XAML

Comments

@daFreeMan
Copy link
Contributor

As a follow on to #4647 (and after installing build .4340) the dialog box still isn't wide enough. The button visibility has been fixed, but that pushed other, arguably less important, information out of the box in its default size:
2018-12-19 08_58_48-rubberduck - add_remove references

I'm running 1900x1200 resolution so there's plenty of room to make that dialogue wider, though I realize that not everyone runs resolution that high (and some are higher).

Would it be possible for the two list boxen to dynamically size themselves to the necessary width, at least until the whole dialogue box reachs some sort of "reasonable" maximum size, say 90% of the VBE window's width? For those with the monitor size, there's no reason not to use it.

Yes, this info is available for each library by selecting it, but if we're going to the trouble of displaying it in the list box, may as well make it visible.

@daFreeMan
Copy link
Contributor Author

An alternative fix would be to have the box remember its size so each user could customize it as (s)he sees fit and we would honor that request.

@Vogel612 Vogel612 added enhancement Feature requests, or enhancements to existing features. Ideas. Anything within the project's scope. user-interface This issue explicitly relates to the visible interface of Rubberduck. up-for-grabs Use this label in conjunction with a difficulty level label, e.g. difficulty-02-ducky difficulty-01-duckling Issue where no particularly involved knowledge of the internal API is needed. good first issue Want to contribute? That's a good place to start! wpf Issue is easier to resolve with knowledge of WPF/XAML labels Dec 19, 2018
@comintern
Copy link
Contributor

Agreed that information shouldn't be hidden on the right hand side. It needs its scrollbars back. Dynamically resizing the form itself would be a little weird (it would also kick the scrollbar out from under the mouse). I think I'd find that behavior surprising as hell.

Definitely needs to persist the window size though.

ShimonLeb added a commit to ShimonLeb/Rubberduck that referenced this issue Dec 26, 2018
bclothier added a commit that referenced this issue Dec 31, 2018
Add HorizontalScrollBar Closes #4662
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
difficulty-01-duckling Issue where no particularly involved knowledge of the internal API is needed. enhancement Feature requests, or enhancements to existing features. Ideas. Anything within the project's scope. good first issue Want to contribute? That's a good place to start! up-for-grabs Use this label in conjunction with a difficulty level label, e.g. difficulty-02-ducky user-interface This issue explicitly relates to the visible interface of Rubberduck. wpf Issue is easier to resolve with knowledge of WPF/XAML
Projects
None yet
Development

No branches or pull requests

3 participants