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

Lines up public variables #3423

Closed
Vitosh opened this issue Oct 6, 2017 · 5 comments

Comments

3 participants
@Vitosh
Copy link

commented Oct 6, 2017

Unfortunately, I do not remember what I was clicking around the tool, but initially I had some public variables in a module like this:
Public Const STARTING_FROM_COLUMN = 6 'In table master, the first column to start writing is column F Public Const COLUMNS_NOT_TOUCHED = 5 'In the table master, the first 5 columns are not touched

After some time the public variables were on one line. It could have been, because some of the comments were with German specific letters like üöäss.

Sorry, that I cannot replicate it now. I was using the indenter, the error checker and pretty much anything around the tool. The error checker was telling me that I was declaring the STARTING_FROM_COLUMN as a Variant (which is true, it should not be a variant).

Cheers! 🌵 💯 👍

@retailcoder

This comment has been minimized.

Copy link
Member

commented Oct 6, 2017

Thanks for reporting, ...but without a repro that one's going to be hard to fix. 😉

@Vitosh

This comment has been minimized.

Copy link
Author

commented Oct 6, 2017

I know. But I do not remember how exactly it happened.

@retailcoder

This comment has been minimized.

Copy link
Member

commented Oct 6, 2017

Could it be related to #3422?

There is no Rubberduck code that intentionally takes two constants on two lines and puts them in a single statement.

@Vitosh

This comment has been minimized.

Copy link
Author

commented Oct 6, 2017

@retailcoder - I dunno, probably. However, I think it was because the comments after the constants were in German. I can only guess. 🦆

@Vogel612 Vogel612 added the stale label Nov 25, 2017

@Vogel612

This comment has been minimized.

Copy link
Member

commented Nov 25, 2017

Closing as stale no-repro

@Vogel612 Vogel612 closed this Nov 25, 2017

@Vogel612 Vogel612 added the bug label Nov 25, 2017

@Vogel612 Vogel612 moved this from Done to NoRepro in Semi-automatic bug tracker Oct 23, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.