You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rubberduck version information
Version 2.5.2.5906
OS: Microsoft Windows NT 6.1.7601 Service Pack 1, x64
Host Product: Microsoft Office 2013 x64
Host Version: 15.0.5215.1000
Host Executable: EXCEL.EXE
Description
After adding a new module mdlDebug to folder 0 General Operations, and a new form frmEditJob to folder 1 Job Operations, neither showed up, despite 8 or 9 refreshes, until a complete restart of Excel. After restarting Excel, mdlDebug and frmEditJob showed up where they should, but there was a new subfolder under 2 Salesperson Operations. It appears as if Rubberduck somehow decided to insert the original 1 Job Operations folder under 2 Salesperson Operations. I did not do any sort of find/replace, rename, or refactor operation that would have caused this.
To Reproduce
Steps to reproduce the behavior:
Truthfully, I'm not sure beyond recreating the entire workbook and code from scratch.
Expected behavior
A clear and concise description of what you expected to happen.
Rubberduck version information
Version 2.5.2.5906
OS: Microsoft Windows NT 6.1.7601 Service Pack 1, x64
Host Product: Microsoft Office 2013 x64
Host Version: 15.0.5215.1000
Host Executable: EXCEL.EXE
Description
After adding a new module mdlDebug to folder 0 General Operations, and a new form frmEditJob to folder 1 Job Operations, neither showed up, despite 8 or 9 refreshes, until a complete restart of Excel. After restarting Excel, mdlDebug and frmEditJob showed up where they should, but there was a new subfolder under 2 Salesperson Operations. It appears as if Rubberduck somehow decided to insert the original 1 Job Operations folder under 2 Salesperson Operations. I did not do any sort of find/replace, rename, or refactor operation that would have caused this.
To Reproduce
Steps to reproduce the behavior:
Truthfully, I'm not sure beyond recreating the entire workbook and code from scratch.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
![image](https://user-images.githubusercontent.com/88000403/186954621-dd244121-9f41-4dd6-b976-a990ffbb0d3c.png)
Logfile
RubberduckLog.txt
The text was updated successfully, but these errors were encountered: