oh I wouldn't have thought of writing "Foo.VarDescription", rather just "VarDescription" and hope it infered it's context by it's position (which, I admit would require some magic)
@M.Doerner, I googled for VB_ExtKey and it only returned 3 results (!!!), none of them really explaining it's purpose or functionality. Is it vb6 exclusive?
> # [Codecov](https://codecov.io/gh/rubberduck-vba/Rubberduck/pull/5404?src=pr&el=h1) Report > Merging [#5404](https://codecov.io/gh/rubberduck-vba/Rubberduck/pull/5404?src=pr&el=desc) into [next](https://codecov.io/gh/rubberduck-vba/Rubberduck/commit/9734c7ff3a1dfd33341a1e877a5e69d52cbd858f?src=pr&el=desc) will **increase** coverage by `0.3%`. > The diff coverage is `86.93%`.
> # [Codecov](https://codecov.io/gh/rubberduck-vba/Rubberduck/pull/5404?src=pr&el=h1) Report > Merging [#5404](https://codecov.io/gh/rubberduck-vba/Rubberduck/pull/5404?src=pr&el=desc) into [next](https://codecov.io/gh/rubberduck-vba/Rubberduck/commit/9734c7ff3a1dfd33341a1e877a5e69d52cbd858f?src=pr&el=desc) will **increase** coverage by `0.32%`. > The diff coverage is `87.19%`.
When working with XAML does any duck know if there's a preference to place a space after a self closing element? IE <TextBlock Text="Foo" /> such that is has a <space> character before the closing />.
This is the function I've written to filter a two-dimension array.
I use it mainly on forms with user-defined filter (categories, dates, search bar, etc).
It works fine, but it's ugly.
Do you have any advice?
Function FilterArray(ByVal originalArray As Variant, _
Optional ...
@this Yeah. TBH, I wasn't quite sure how I felt about the project... You know, is it viable, does it work, are the devs responsive... I just needed to check it out for a while...
> I think in the situation of the MCVE, we really should issue a result. There is no reason why to treat private variables in interfaces any different than private variables in any other components.
For public fields, the situation is a bit different. We do not report interface members with an implementation as not used, even if they are never used. However, we report public fields on interfaces with an implementation. That is inconsistent. However, I would like to propose to actually report
@this Yeah, saw that. Wonder how many years ago they tried it out. Granted, still not the fastest thing in the world, but light years better than 2.0 versions
@this That's me. Oh, I guess it was the shooting star part, not the "The more you know" part. I was cornfused
@Cyril all those things listed over there --> are starred comments. Just to the left of the "reply to this message" arrow is the "star this as interesting" star. We really don't necessarily use it for that. At one point any "lol" message was starred about 20 times...
And Duga's message about starring us is her notifying the chat that someone has clicked the GitHub star to follow the project.
You know... When I was a kid, we didn't have to be told "do not try this at home" about every single thing we saw on TV. A) we weren't stupid enough to try, or B) if we were, our parents would look at us and say "well, that's what you get for being stupid enough to try"...
Consts and literals are fine enough. I'm just saying that you can pretend that consts are basically "public" literal (e.g. they are treated the same way as a literal, but without having to use the magic numbers every where)
This is the function I've written to filter a two-dimension array.
I use it mainly on forms with user-defined filter (categories, dates, search bar, etc).
It works fine, but it's ugly.
Do you have any advice?
Function FilterArray(ByVal originalArray As Variant, _
Optional ...
VBA Rubberducking
VBA Rubberducking