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

Not able to enter Spaces after Parsing #5545

Closed
rentasad opened this issue Jul 23, 2020 · 4 comments
Closed

Not able to enter Spaces after Parsing #5545

rentasad opened this issue Jul 23, 2020 · 4 comments
Labels
bug Identifies work items for known bugs

Comments

@rentasad
Copy link

Rubberduck version information
The info below can be copy-paste-completed from the first lines of Rubberduck's log or the About box:

Rubberduck version 2.5.0.5244 loading:
Operating System: Microsoft Windows NT 10.0.18363.0 x64
Host Product: Microsoft Office x86
Host Version: 16.0.13001.20384
Host Executable: EXCEL.EXE;

Description
After parsing my big project in the IDE I'm not able to enter a space.
My Log is attachted here:

RubberduckLog.txt

I will show you the problem in my Video:

https://youtu.be/7ImDDuFHqqw

in an empty project I don't have this problem - my huge Project have this problem and I don't know why...
I hope you have an idea to find the reason for it?
Best greetings!

Rentasad

@rentasad rentasad added the bug Identifies work items for known bugs label Jul 23, 2020
@daFreeMan
Copy link
Contributor

Define "huge project". How many modules? How many lines of code?

Try updating to the latest pre-release (build .5508 as of today) to see if that fixes the issue. I've got a decent sized project and am not having any issues like that. Huh... only 8300 LOC over 49 modules in this Access project. No issues with build .5508 when working in Excel a couple of days ago, either.

Pre-releases are generally pretty stable and are suitable for a busy, full-time programmer. There is the occasional show-stopping bug that will force you to back up to the previous pre-release, but those are usually fixed pretty quickly.

@MDoerner
Copy link
Contributor

Thanks for reporting.

There was indeed a subtle issue with the UI, both for the test explorer and the inspection results that could cause a freeze in some projects. This specific issue has been fixed in the meantime. So, could you try out the current prerelease and see whether that fixes your problem? Otherwise, you will have to wait until the next stable release to see whether the problem still exists for you.

@rentasad
Copy link
Author

I will try it and will report if it was helpfull. Thanks for your quick reply!

@rentasad
Copy link
Author

Hi,
today I completed my integratoin ovf code --> I don't get the error anymore -> the build .5508 fixed the problem
Thanks and best regards
Matthias//Rentasad

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Identifies work items for known bugs
Projects
None yet
Development

No branches or pull requests

3 participants