Rubberduck Statusbar Show on load settings

[MikeAndLisa]

When I use rubberduck it takes up a line of it's own in the VBE reducing the code window. I always untick it from the toolbar menu until I want to use it. This is not persistent. When I open the VBE again or in a different application then I have to untick it again... and again.... and again...... Please make unticking rubberduck persistent for when opening the VBE.

Mike Green

[bclothier]

This is actually by design because the status bar can take lot of space, so the button is always "temporary" and added to its own line to ensure there is enough space to display all the data.

That said, this can be an enhancement to not show it by default until you actually parse via the menu items.

[retailcoder]

IIRC we made it temporary as an attempt to reduce the number of things that could go wrong on teardown, in 2.0.x; might not be warranted anymore.

[MikeAndLisa]

That would be good…. And save me some frustration too!

Why not a separate dockable toolbar that can be switched on and off like most of the others? In fact… all of them I think.

Thanks Mike

Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10

---

From: bclothier notifications@github.com Sent: Tuesday, October 23, 2018 5:42:47 PM To: rubberduck-vba/Rubberduck Cc: MikeAndLisa; Author Subject: Re: [rubberduck-vba/Rubberduck] Rubberduck persistence (#4453)

This is actually by design because the status bar can take lot of space, so the button is always "temporary" and added to its own line to ensure there is enough space to display all the data.

That said, this can be an enhancement to not show it by default until you actually parse via the menu items.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/rubberduck-vba/Rubberduck/issues/4453#issuecomment-432297563, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AqRCY6ErFj0HzVxc-ddbwIUsSeXJ6Wwbks5unzj3gaJpZM4X116j.

[retailcoder]

We're explicitly creating & destroying the toolbar because letting the VBE do it easily translates into leaked objects and serious problems on teardown.

IMO best we can do is to add a setting to optionally keep it hidden by default. VBE docking and window/workspace persistence isn't exactly cooperating nicely with VBE extensibility, and has zero chance of ever being improved by Microsoft.

Keep in mind we're a .net application from 2018 interacting with COM tech from 25 years ago.

The idea for the commandbar has always been to be like a "status bar" (which I'm sure you noticed, the VBE lacks), providing context-sensitive selection info that tells us what Rubberduck is seeing at the selected position. Having it in sight at all times is completely by design.