« first day (2342 days earlier)      last day (838 days later) » 

Duga
Duga
12:01 AM
RELOAD!
[rubberduck-vba/Rubberduck] 11 commits. 1 opened issue. 3 closed issues. 5 issue comments. 9762 additions. 3379 deletions.
[Zomis/Games] 6 commits. 1 opened issue. 1 closed issue. 6 issue comments. 115 additions. 31 deletions.
[Minesweeper] Games Played: 171, Bombs Used: 128, Moves Performed: 22497, New Users: 6
 
 
3 hours later…
Mathieu Guindon
Mathieu Guindon
2:53 AM
Woohoo! I had to download and install the .net core runtime onto my work laptop, but I got the dang thing to run and update the xmldoc assets and download counts
looks like the "new!" logic for inspections kinda works
...and is borked for annotations lol
 
BigBen
BigBen
lolol
always good when you have a Woohoo moment followed by a borked one.
 
Mathieu Guindon
Mathieu Guindon
3:13 AM
eh, just happy I found the darn exe, first one I recovered was a debug build from May... didn't feel right, crashed, got me worried lol
 
 
2 hours later…
Duga
Duga
4:45 AM
> **What**
An inspection that locates call sites for the `VBA.Information.VarType` function, and flags a direct `=` check as problematic when the operand is `VbVarType.vbArray`. Although, it probably doesn't hurt to flag any direct `=` comparison from the return value of `VBA.Information.VarType`, either.

**Why**
The enum value returned by the `VarType` function requires bitwise comparison to evaluate as intended: as written, the condition is systematically false given a `Variant()` (varian
> 💡 there has to be a way to make that quick-fix readily applicable to any = operator involving Enum operands...
> 💡 there has to be a way to make that quick-fix readily applicable to any `=` operator involving `Enum` operands...

<sub>(without there necessarily being an inspection result)</sub>
 
Duga
Duga
5:08 AM
Modify to eliminate underscore from incremented Identifiers

Using an underscore strategy generates Property identifiers that are disqualified from participating in interfaces (without renaming).
Merge pull request #5607 from BZngr/RemoveGeneratedNameUnderscores

Modify EncapsulateFieldRefactoring to generate Identifiers without underscores
 
Duga
Duga
5:29 AM
[rubberduck-vba/Rubberduck] build for commit 54567b4f on next: AppVeyor build succeeded
 
Duga
Duga
5:54 AM
> Closing this would be monolithic PR in favor of smaller more targeted ones.
 
Duga
Duga
6:09 AM
> Close #4541.
> Close #4541. Was a starting point at the beginning of the alphabet. This may be better split into further subdivided resource files.
> Close #4541.
> Close #4541. This is another PR one that may benefit from being broken down further into even more specific files.
[rubberduck-vba/Rubberduck] build for commit c1e108a7 on unknown branch: AppVeyor build succeeded
> Close #4541.

This PR still has an EmbeddedResource commented out to allow building.
> Close #4541.
[rubberduck-vba/Rubberduck] build for commit e6c9912e on unknown branch: AppVeyor build succeeded
> Close #4541.
 
IvenBach
IvenBach
6:57 AM
Sorry if I took those PR in the wrong direction.
 
Duga
Duga
7:13 AM
[rubberduck-vba/Rubberduck] build for commit 3e949303 on unknown branch: AppVeyor build succeeded
 
Duga
Duga
7:33 AM
[rubberduck-vba/Rubberduck] build for commit efa09053 on unknown branch: AppVeyor build succeeded
 
Duga
Duga
7:56 AM
[rubberduck-vba/Rubberduck] build for commit 86fb1db9 on unknown branch: AppVeyor build succeeded
 
Duga
Duga
8:09 AM
> Version 2.5.1.5632
OS: Microsoft Windows NT 10.0.19041.0, x64
Host Product: Microsoft Office 2013 x86
Host Version: 15.0.5267.1000
Host Executable: MSACCESS.EXE


**Description**
On my Access Projects I couldn't use rubberduck, because on "refresh" the is a unexcepted error.
For verification I created a new access 2013 accdb Database with a new form, one button with minimal code - there is also this error

**To Reproduce**
Steps to reproduce the behavior:
1. Create a new access pr
[rubberduck-vba/Rubberduck] build for commit 76d745a0 on unknown branch: AppVeyor build succeeded
 
Duga
Duga
8:39 AM
[rubberduck-vba/Rubberduck] build for commit 176a4f84 on unknown branch: AppVeyor build succeeded
 
 
2 hours later…
Duga
Duga
10:59 AM
> I understand the use of warning against direct comparison to `vbArray`, but I do not like the idea to flag it for any other value.
Why should `VarType(foo) = vbLong` be suspicious, if I want to test whether the variable `foo` contains a scalar of value type `Long`? If `And` this with `vbLong` I might get an array, which is probably not what I want since I would have to access it a different way than a scalar.
> Thanks for reporting this. I have an idea what is going wrong and will look into it this evening.
 
Duga
Duga
11:23 AM
> The real problem is that the VbVarType enum is not just a bitmask. It has non-flag members with few flag members. Therefore, the case of VarType(someVariant) = vbLong would fail if my intention was to assert whether I had a Long value or an array of Long values before proceeding. Your point about requiring different access is well-taken but it won't change the fact that if I have a Variant parameter and I need to support both a scalar value and array value but still assert that it's
 
this
this
11:33 AM
Why would git reported that a pull was successful but then leave me with uncommitted changes?
 
Duga
Duga
 
Duga
Duga
12:04 PM
[rubberduck-vba/Rubberduck] build for commit a8b817aa on unknown branch: AppVeyor build succeeded
 
Duga
Duga
12:16 PM
 
Vogel612
Vogel612
12:50 PM
@this pull is not commit?
Why would you expect pull to commit things?
Pull just fails for conflicts, it can deal just fine with non-conflicting uncommitted changes
 
this
this
1:02 PM
but, i started with no changes, pulled from next, and was told merge was successful, no conflicts.
then when i checked status there were two edited files
 
FreeMan
FreeMan
Because Monday! Oh... wait... Because Election Day!
 
this
this
I wasn’t expecting there would be uncommitted changes just because I pulled?
@FreeMan i hope it will be a day, rather than a week or worse, a season....
either way gonna be an entertaining time, for some value of entertaining
 
FreeMan
FreeMan
@this Yeah, I get ya'. I have a feeling that "election season" will run just as long as "covid-season". Though, once the election is finalized, I have a feeling covid will magically disappear
 
this
this
i think it will too. its overpoliticalized, if there is such concept
 
FreeMan
FreeMan
I'll take "things that aren't over politicized" for $1000, Alex. (Pretty sure the board was long ago cleared of those items...
 
Duga
Duga
1:46 PM
 
Duga
Duga
2:28 PM
> Also to be taken into account: non-equality checks involving a <> operator, which would be similarly "always true" (the fix could be the same just surrounded with a Not operator, or the bitwise logic can be flipped - either works)
 
Duga
Duga
2:55 PM
 
Duga
Duga
3:29 PM
[rubberduck-vba/Rubberduck] build for commit 61d644b9 on unknown branch: AppVeyor build succeeded
 
Duga
Duga
3:52 PM
 
Duga
Duga
4:06 PM
[rubberduck-vba/Rubberduck] build for commit 2f85e273 on unknown branch: AppVeyor build failed
BUILD FAILURE!
 
Duga
Duga
4:23 PM
 
Duga
Duga
4:51 PM
[rubberduck-vba/Rubberduck] build for commit 73fde358 on unknown branch: AppVeyor build failed
BUILD FAILURE!
 
M.Doerner
M.Doerner
Has anybody other than me also experienced that we no longer have a Rubberduck context menu item for the code pane?
 
Duga
Duga
 
this
this
@M.Doerner haven't seen that, sorry.
 
Mathieu Guindon
Mathieu Guindon
5:06 PM
Hm, I'm still on an older 2.5.1 release build, all menus are where they should be
 
Duga
Duga
5:23 PM
[rubberduck-vba/Rubberduck] build for commit 49e2b134 on unknown branch: AppVeyor build succeeded
 
FreeMan
FreeMan
@M.Doerner I'm on .5632 and I see the context menu when clicking in the code pane in Access.
Though Add/Remove References is disabled for no discernible reason
but I have been getting an Unexpected Error on parse... Issue incoming...
Which appears to have been reported already
 
Duga
Duga
 
IvenBach
IvenBach
5:42 PM
@M.Doerner Just merged with upstream/next Version 2.5.1.17280 and I have RD's context menu.
 
Duga
Duga
5:55 PM
[rubberduck-vba/Rubberduck] build for commit 1741a26b on unknown branch: AppVeyor build succeeded
 
Duga
Duga
6:19 PM
 
 
3 hours later…
Duga
Duga
9:22 PM
 
Duga
Duga
10:16 PM
> Closes #5624

Materialize additional supertype interfaces before adding them to the collection they are based on.

I should have tested this on Access, but apparently didn't. On Excel, the problem does not surface since this interface construction is specific to Access.
 
M.Doerner
M.Doerner
Hm, here on my personal machine, I have the context menu, but not on my work machine running the last stable release.
 
Duga
Duga
10:37 PM
[rubberduck-vba/Rubberduck] build for commit 1a025719 on unknown branch: AppVeyor build succeeded
Materialize additional supertype interfaces before adding them to the interfaces

The additional supertypes are derived via a LINQ expression on the interfaces. So, none cannot add the enumerable directly as this changes the enumerated collection.
Merge pull request #5625 from MDoerner/FixBugInSuperTypeNameDetermination

Fix bug in supertype name derivation
 
Duga
Duga
10:56 PM
> [DefaultMemberUsage.xlsx](https://github.com/rubberduck-vba/Rubberduck/files/5484505/DefaultMemberUsage.xlsx)

Collated some usage data regarding the default `Declaration` interface. Perhaps interesting...perhaps not.
[rubberduck-vba/Rubberduck] build for commit 0dd180ee on next: AppVeyor build succeeded
 
mansellan
mansellan
The VB runtime is a VM right? So let's just skip VB(A) and implement a new language that compiles p-code for the VM to eat, and (just for giggles) hijacks the VBA storage API too, so that it can be written into IStorage hosts. How hard could it be?
(sorry. It's Tuesday, I'm bored, and trying not to think about what happens in the US in the next few hours)
 
this
this
11:12 PM
what about document modules and 64-bit VBA (no 64-bit VB6)
 

« first day (2342 days earlier)      last day (838 days later) »