« first day (2292 days earlier)      last day (81 days later) » 

12:01 AM
[rubberduck-vba/examples] 4 commits. 2388 additions. 1 deletion.
[rubberduck-vba/Rubberduck] 1 opened issue. 1 closed issue. 3 issue comments.
[Minesweeper] Games Played: 123, Bombs Used: 80, Moves Performed: 17416, New Users: 19
5 hours later…
5:02 AM
@BloggingDuck more bird droppings from Mug!
Look forward to a fresh mind reading it tomorrow.
peterkretzman.com/2012/10/23/… Was a good read about not following cargo cult mentality on avoiding comments entirely.
Use them in moderation, where appropriate.
2 hours later…
7:07 AM
4 hours later…
11:36 AM
@IvenBach Zip Drives! Ahhh... the Click of Deathâ„¢. I had a couple of Zip Drives. One spent about 10 years under my wife's desk, connected to her computer. I used it as a parallel port cable extender to reach from the computer at one side to the printer at the other side of her desk. Oh, yeah, I'd also used it for its intended purpose of transporting a gargantuan 100 Megabytes of data from place to place, too!
@IvenBach "bird droppings"? Is that what you think of Mug's pearls of wisdom? You'd better apologize before the bird droppings hit the fan!
@FreeMan yeah! Iven should know better than to call a duck a bird!
12:50 PM
Code and comments. The code should clearly describe WHATit is doing. The comments should provide a clear description of WHY.
1:03 PM
IMO, the real problem is usually when the code changes without changing the comments. There is no mechanism that forces you (besides your own discipline) to keep the comment in sync with the changed code. For that reason, eliminating comments by writing self-describing code can help a lot. But you're correct; there will be times where we need to describe the "why" especially when doing something that might be perceived as strange.
There's just no way to guarantee the comment will stay in sync with changes.
Tangentially, I'm inclined to think the lower you go in the language's abstraction (e.g. C or C++), the more comments & documentation you'll need because there are more assumptions that will be implicit and not enforced via the code itself.
1:24 PM
> **Rubberduck version information**
Rubberduck version loading:
Operating System: Microsoft Windows NT 10.0.14393.0 x64
Host Product: Microsoft Office x86
Host Version: 16.0.12527.20880
Host Executable: MSACCESS.EXE;

We are in the processes of moving our Access to a Remote Desktop Services model with all Access applications centralized on a remote server. Through this model I hav
1 hour later…
2:37 PM
> Hey all,

Has rubberduck got a way of unit testing class event handler calls?


Dim withEvents obj as SomeClass
set obj = new SomeClass
set objTracker = Fakes.trackEvents(obj)
Debug.Print objTracker.called("beforeDoSomething")
Debug.Print objTracker.called("afterDoSomething")

If not what's the work around? Should we be creating a class and tracking this more directly?

Dim WithEvents obj as new SomeObject
Dim called as new collection
Which path do we use as the Rubberduch_TEMP_PATH?
@Duga ^^ might be missing write permissions to the temp folder.
3:16 PM
@FreeMan just Mug dropping wisdom on us far below.
Well, then, @IvenBach, those are "Mug drippings" not "bird droppings"!
1 hour later…
4:21 PM
@M.Doerner I can't find this ATM but I am pretty sure a similar error was reported before. It's to the temporary directory but there are apparently edge case where the folder isn't created (or was created but then subsequently deleted) that cause the error.
@FreeMan sounds painful... Possibly lethal.
I know that it was because of missing folders before, but we have code that adds the folder now.
what I do not remember if we actually handle the case where path changes (or if it's relevant still)
You got the wrong issues. I found two other issues by googling the hresult.
The only results are for our issues.
One got closed after @MathieuGuindon added code that checks whether the folder is there and creates it if not right before the export call.
That is what made me think there might be permission issues.
AFAIU, that error basically says "Can't write to filesystem.".
When did we release 2.5.0?
Hm, that's not it. The fix is from Feb 2019.
3 hours later…
7:41 PM
2 hours later…
9:15 PM
ugh, why must you suck, Mister Monday?
I'm right there with you.
the small respite is that Mister Monday is almost done.... at least for a week. But we'll have to deal with Mister Tuesday soon.
10:15 PM
> It's just a small formatting change. That means a quick edit. Right?
^ :barf:
11:06 PM
Methinks autocompletion needs to convert foo == bar into foo = bar.
I've developed C# habits that now leak into VBA coding.

« first day (2292 days earlier)      last day (81 days later) »