« first day (2365 days earlier)      last day (55 days later) » 

12:01 AM
RELOAD!
[rubberduck-vba/Rubberduck] 1 opened issue. 1 closed issue. 7 issue comments.
[Zomis/Games] 1 commit. 1 opened issue. 3 additions. 3 deletions.
[Minesweeper] New Users: 16, Games Played: 99, Bombs Used: 51, Moves Performed: 14650
 
mumble mumble github.com/rubberduck-vba/Rubberduck/blob/next/… barfing on exception...
> Key not found in dictionary.
Time to figure out which one.
False alarm. Some other inspections are lacking their keys.
¿Is a worksheet object not a DocObject? Is that the root cause?
 
12:26 AM
I think they are classes.
You can identify them by being a class module with supertype Worksheet.
Btw, have you added the default severity and category in the setting file?
 
12:42 AM
I have not.
Still trying to get the issue to show in Issues Explorer.
As frustrating as this is I'm learning and have to struggle through it to increase my understanding.
 
12:59 AM
mumble mumble RelevantDeclarationsInModule return results as expected.
@IvenBach Correct. declaration.QualifiedModuleName.ComponentType evaluates to Document.
mumble mumble write the test first they say. mumble mumble need to mumble understand correctly mumble back into correct answer mumble.
github.com/rubberduck-vba/Rubberduck/blob/next/… looks like execution should next be line 171 RunInspection. The member immediately beneath it.
Execution jumps back up to line 100 on a local variable definition inspectionsToRun.
That variable assignment includes a LINQ Where(...) statement.
Do I understand correctly that execution/evaluation of that predicate used in Where does not occur until that IEnumerable<T> is iterated over, caused by the Parallel.ForEach(...).
I'm assuming that's the case as inspectionsToRun is an argument to RunInspectionsInParallel(...). That's the only thing that makes sense in this case.
And for all others where there is an apparent jump to another block of code on iterating each member.
mumble mumble captured variable mumble closure? Vague brain tickle of docs I didn't fully understand when I read them.
@M.Doerner Where can I accomplish that?
 
1:25 AM
@IvenBach Aside: DocObject is a VB6 thing. Not same thing as DocumentModule.
 
That is exactly what I thought it was on seeing a result in the inspections list. Hence my rubberducking my thought process.
Doing everything I can to understand it on my own.
@this you available?
 
1:52 AM
> Closes #5608.

Should this be expanded to handle all class modules? I'm fine with an Enum being defined in a class module.
 
2:11 AM
 
[rubberduck-vba/Rubberduck] build for commit 7019b396 on unknown branch: AppVeyor build succeeded
 
 
1 hour later…
 
10 hours later…
1:16 PM
<pedantMode> it's 'fell into a hole'. 'Fell in a hole' means I was in a hole then I fell (over)</pedantMode>
 
 
5 hours later…
6:52 PM
> Not the OP, but in my case, macro in Word, simply printing one or more empty lines to immediate window:

```
Sub PrintEmptyLine(Optional ByVal Pocet As Long = 1)

Dim i As Long
For i = 1 To Pocet
Debug.Print ""
Next i
End Sub
```

Written like this, it doesn't trip the inspection. Using plain and simple `Next` without the `i` variable, I get the "variable not used" as well.
> Not the OP, but in my case, macro in Word, simply printing one or more empty lines to immediate window:

```vba
Sub PrintEmptyLine(Optional ByVal Pocet As Long = 1)

Dim i As Long
For i = 1 To Pocet
Debug.Print ""
Next i
End Sub
```

Written like this, it doesn't trip the inspection. Using plain and simple `Next` without the `i` variable, I get the "variable not used" as well.
 
 
1 hour later…
7:54 PM
Erm debug.print vbcrlf & string$(Pocet-1,vblf)
 
8:19 PM
@Duga I should have fixed that for some time already, but I do not find any time for it for some reason.
 
 
2 hours later…
10:47 PM
 

« first day (2365 days earlier)      last day (55 days later) »