> @tallguyjenks make sure you picked up the latest pre-release build - if you haven't been following the [project's blog](https://rubberduckvba.wordpress.com) or [social media](https://m.facebook.com/story.php?story_fbid=2266342446982944&id=1570311533252709) posts there's a big surprise feature currently in pre-release!
> Which references do we want included in the search results for this? The current method in the `DeclarationFinder` for identifying if a reference is "used" looks at all identifier references for the library and all uses of its declared types (i.e. `Dim Foo as Worksheet`). We could easily do that, but for an enormous project, that might make for an... extensive... list of results for the host project, and probably even more for the VBA reference.
> I wouldn't exclude any libraries... could identifier refs be cached by typelib in [yet another] dictionary? That could simplify the code that identifies unused libraries.
> I'm don't think the un-cached performance is really that bad ATM. I was mainly coming at it from the standpoint of Find all references... --> OK, here's a dialog with a couple thousand results.
> In the grouping grid in the `InspectionResultsControl` we bind to the `Result` collection on the view model, which is an `ObservableCollection<IInspectionResult>`, and base the grouping on the `Inspection` property of the items. Since `IInspectionResult` does not extend `INotifyPropertyChanged` this leaks all inspection results.
The cleanest way to fix this is probably to introduce an `InspectionResultViewModel` that implements `INotifyPropertyChanged` to wrap the results.
> As an alternative to the additional view model, we could change the binding mode to OneTime, which makes the UI use a snapshot and avoids registration to the value changed event.
@Comintern not often that one expects a failure and then is disappointed
Got my copy of Head First C#: A Learner's Guide to Real-World Programming with C#, XAML, and .NET last night. That's a tome! When I'm done with it, I'll use it to prop up the wobbly couch.
I got through the preface last night. Not sure I'll really dig into it before Christmas, but after, it's on
Speaking of which, I may need @WaynePhillipsEA help. I get a null reference exception deep within mscorlib when calling Marshal.GetTypeForITypeInfo on a VBA's ITypeInfo, though the pointer is valid.
it's nto an Access only problem. I've seen it in VBE in general.
It might be that you see it more in Access because if you are saving your code while you're in break mode, and possibly with open Access forms in design view, you end up saving the breakpoints into the stream.
Since I know know a good way to fix the problem, I probably won't worry about the cause too much, but getting into a better habit is a good thing to do
changing Dim statements automatically stops execution anyway. Though you get a lovely little warning
> Of those options, it seems like the more reasonable one (at least in the short term) would be to switch to `OneTime` binding. I'd assumed that was what we were doing but that's apparently not the case. I can't really think of a situation where an inspection result would "change" with our current inspection architecture unless the entire `ObservableCollection` was being replaced.
If we ever do change the overall architecture to allow more dynamic inspection, that would be the time to add an
Imo, it can save time when developing. I find myself often modifying an expression, then dragging the execution pointer up again, then F8. But I usually finish or stop the run before I save.
Might only be me, though. (Looking at my 2-year-old spaghetti... it takes time to get to that certain point in the code...)
Thus the setting. I'd personally keep it on to prevent myself from doing things like editing out a loop exit condition or changing a pointer for an API call (both of which can take a host down).
@Inarion It's the two---three dashes but there ---can't be needs to be a space at the "outside" edges of the dashes
ha!
the space between the --- and be--- needs were the triggers for the strikethrough
OK, just 'bout time for the next pig-out fest. Company Department Christmas gathering. Then tomorrow starts vacation. But the boss scheduled me into a meeting at 3:30 this afternoon... :(
Salut, moi aussi je suis bilingues, avec l'avis d'un marabout je te conseille de vendre ton âme au plus offrant et de rajouter du sel autour de ton espace de travail, cela éviteras d'attirer les démons du code de merde. En effet le code de merde sais ce que tu nous sort la espèce de Bic mac à qua...
> Version 2.3.1.4340 OS: Microsoft Windows NT 10.0.15063.0, x64 Host Product: Microsoft Office 2016 x64 Host Version: 16.0.4711.1000 Host Executable: MSACCESS.EXE
if there's only 1 project opened, they're the same thing. if there's 2 or more projects, "all detected occurrences" affects all projects that spawned a result for that inspection
@FreeMan lol. I saw Common HRESULT values and assumed it was a generic. It is in fact generic, not just for cryptography; but I guess they decided to re-list those in their documentation.
@this I googled a hex converter and it ignored the -. Well, actually, it stuck it on the beginning of the string it returned. Guess it's not that good a converter...
that's not turning up much either. Most of what I'm finding is related to issues with Windows when updating from Win7 to something newer...
This is in a method that loops through all the pivot tables on a worksheet and refreshes them, so it's probably related to that, but I don't have a clue how...
I'm getting a Parameter 'x' can be passed by value inspection for a class parameter in the Interface definition.
I suppose this is correct because A) it's a class so it doesn't really matter whether it's ByRef or 'ByVal`, I'll still get my data back. But B), a property of the class is assigned to in at least one of the implementations.
I get that I can pass this ByVal and it will still work, but somehow this seems wrong.
Is it simply because I've got a case short-timer's since today is my last day before vacation?
> I just installed RD to a non-admin user on a new PC,64 bit Excel 2016 in O365. The Add-in Manager shows it Loaded, and on Startup. but there is no Rubberduck menu in the VBE. I unchecked and rechecked Loaded but it did not appear. Should I reinstall as admin?
> I just installed RD to a non-admin user on a new PC,64 bit Excel 2016 in O365. The Add-in Manager shows it Loaded, and on Startup. but there is no Rubberduck menu in the VBE. I unchecked and rechecked Loaded but it did not appear. Should I reinstall as admin?
Yeah. in other news, I just ran into something weird... the CE's "add" menu items all disappeared. one minute they were there, the next they weren't. no idea what happened.
i'm trying to write a test module to test one of the modules I wrote. In specific, I have a if statement I would like to trigger using the test module by giving the module the wrong initial parameters. The module I would like to test is:
Function TPR_TNR_FPR_FNR(expected_vals As Range, pred_vals...
You're going to need to leverage the Rubberduck Fakes API in order to cover the code paths involving MsgBox - otherwise these tests will pop a msgbox, which you don't want in an automated unit test. Alternatively, throw an error and let the caller show the msgbox, and test for that specific error being raised given invalid inputs. — Mathieu Guindon22 secs ago
Would it be too specific to have an inspection that flags Range.Select calls passed as arguments to anything?
VBA Rubberducking
VBA Rubberducking