VBE Help: Size of code pane

[Ailish]

I'm not sure I have the terminology correct so bear with me please.

Is there a way to set a default size for all code panes?

By code panes, I mean the "windows" that open in the VBE when an existing
module or form is double clicked, or when Insert Form or Insert Module is
clicked.

The reason I'm asking is that I frequently find that the window is so wide
that I can't see the x to close a userform or module. I frequently have to
click and drag the whole window to the left in order to bring the x into
view. These windows open so wide that there are acres of unused white space.
I resize them to fit the available grey space but they seem to have minds of
their own and eventually default to the 'too wide' size again. I can't make
sense of it - particularly as my monitor is a widescreen one so it seems all
the more weird.

It's such a small problem but it's irritating! I've investigated just about
every button but can't find a way to choose the size. (I know how to set the
size of a Userform - that's not what I'm talking about - it's the white space
behind the Userform in Design View that I'd like some control over.)

Am I the only one with this problem? Has anybody got a solution?

 

[Doug Robbins - Word MVP]

I think it may be more likely something to do with your graphics
card/display settings

--
Hope this helps.

Please reply to the newsgroup unless you wish to avail yourself of my
services on a paid consulting basis.

Doug Robbins - Word MVP, originally posted via msnews.microsoft.com

 

[Ailish]

If that were the case, I'd have thought the problem wouldn't be confined to
the Microsoft Visual Basic Editor - but it is. I use a few programmes that
have parent & child windows but none have this problem.

 

[Fumei2 via OfficeKB.com]

I do not think this is exposed for any meaningful choice. I sure as heck can
not find anything to affect the default code window size.

It is a little annoying I suppose. It seems the window (for a userform) - at
least for me - is double the default width of the default userform.

I think you may be out of luck on this one.

If that were the case, I'd have thought the problem wouldn't be confined to
the Microsoft Visual Basic Editor - but it is. I use a few programmes that
have parent & child windows but none have this problem.

I think it may be more likely something to do with your graphics
card/display settings

[quoted text clipped - 30 lines]

 

[Jay Freedman]

I don't think the default size is settable. To save some aggravation,
instead of dragging the windows around, click Window > Cascade to force all
the child windows to fit inside the parent window.

Now, I'd be happier if the VBE will ever be made aware of dual monitors, so
the userform Controls box appears somewhere near the userform instead of
over in the next county...

--
Regards,
Jay Freedman
Microsoft Word MVP
Email cannot be acknowledged; please post all follow-ups to the newsgroup so
all may benefit.

I do not think this is exposed for any meaningful choice. I sure as
heck can not find anything to affect the default code window size.

It is a little annoying I suppose. It seems the window (for a
userform) - at least for me - is double the default width of the
default userform.

I think you may be out of luck on this one.

If that were the case, I'd have thought the problem wouldn't be
confined to the Microsoft Visual Basic Editor - but it is. I use a
few programmes that have parent & child windows but none have this
problem.

I think it may be more likely something to do with your graphics
card/display settings

[quoted text clipped - 30 lines]

Am I the only one with this problem? Has anybody got a solution?

 

[Karl E. Peterson]

I'm not sure I have the terminology correct so bear with me please.

Is there a way to set a default size for all code panes?

The default, such as it is, should be what you see if you start a brand
new project and open a window in that. But it seems that once a
particular module is opened, the editor recalls where you had it last
and repositions it there when you re-open it. In ClassicVB, we delete
the project's VBW file to erase that memory. In VBA, my best guess
would be that you need to run one of the Code Cleaners available on
that project. Interesting question.

The other options are to get used to just maximizing these "corrupt"
project code windows and/or stop moving projects from systems with
large monitors to systems with small monitors.