« first day (2018 days earlier)      last day (38 days later) » 

12:01 AM
RELOAD!
[MDoerner/AdventOfCode2019] 2 commits. 1387 additions.
[Phrancis/AdventOfCode2019] 2 commits. 215 additions. 22 deletions.
[rubberduck-vba/Rubberduck] 1 opened issue.
[Zomis/AdventOfCode] 2 commits. 196 additions. 11 deletions.
[Zomis/Duga] 5 commits. 5 closed issues. 7 issue comments. 209 additions. 59 deletions.
[Minesweeper] Games Played: 70, Bombs Used: 52, Moves Performed: 8567, New Users: 23
 
12:17 AM
@BloggingDuck From what I've seen so far this felt easier to understand than the guide on the wiki.
Just a little more thorough in helping the less initiated understand what is going on.
Something like this:
Member-level annotations apply to the entire procedure they’re annotating, and must be located immediately over the procedure’s declaration
Nice touches that make it less frustrating.
 
note that "immediately above" can (and has been) misunderstood as meaning the line directly above
 
 
1 hour later…
1:38 AM
so there can be arbitrary whitespace?
 
2:19 AM
[rubberduck-vba/Rubberduck] build for commit c0e49f57 on next: AppVeyor build failed
BUILD FAILURE!
 
2:55 AM
[rubberduck-vba/Rubberduck] build for commit c0e49f57 on next: AppVeyor build failed
BUILD FAILURE!
 
@theVBE-it'srightforme yep. And that can make it part of the declaration or the member. IIRC
The drop downs at the top of the coding pane indicate where they belong to. The white bar separating members also.
With default colors it’s the black line.
 
 
1 hour later…
4:26 AM
@IvenBach so basically just treated conceptually like a comment. that makes sense.
 
 
6 hours later…
10:45 AM
AFAIR, I implemented it such that member and variable annotations attach to the next member or variable.
And module annotations can be anywhere above the first member.
The one remaining point that is confusing for a lot of people is that attaching annotations, especially @Ignore, is based on the physical line and not the logical line.
@IvenBach What the VBE thinks is the declaration section is entirely irrelevant to the annotations.
 
 
6 hours later…
5:06 PM
> Yes I frequently switch to Excel to find the "find symbol" dialogue open; didn't realise this was the cause, but sounds plausible
 
5:25 PM
@MathieuGuindon Blergh, I just realized that @Duga is still keeping track of this:
in Duga's Neighborhood, 18 hours ago, by Duga
Mathieu Guindon vs. Simon Forsberg: 17262 diff. Year: +1242. Quarter: +509. Month: +129. Week: +99. Day: +10.
 
@SimonForsberg LOL!
 
5:37 PM
...wait was that set up for the race to ...20K?
 
@MathieuGuindon Nah, it hasn't been there for that long. I deactivated it at some point, and then I activated it again, and then I switched the room for it to her debug room as I was sick of seeing how far ahead you were
 
mwahaha
 
6:22 PM
@BloggingDuck '... Code Explorer will display these modules with a dedicated “interface” icon. ' Do we want to include that icon in the post or forgo it in case the icons later change?
Giving it more thought not including the icon makes more sense for that very reason of changing icons.
TYVM for taking the time to write the annotations post. Very helpful knowing more of the inner workings and how to properly use them.
I'd make the change suggesting that all ExcelHotkeys include the Shift modifier key. This is because every key Ctrl+FooKey is used for a default excel hotkey.
 
7:11 PM
@IvenBach not true. all hotkeys include ctrl, only uppercase letter makes it include shift =)
 
~.~ #Words.
 
 
2 hours later…
9:30 PM
RELOAD!
[testing] 42 AWS Tests Succeeded. 5 Duga functions migrated to AWS. 4 Duga functions that is actually being used on AWS
 
@M.Doerner not as confusing as @Ignore only skipping code inspections and not allowing you to exclude a module from parsing/resolving when it is throwing a bunch of errors you don't want to worry about fixing immediately
@MathieuGuindon on that note I have a question - how do hotkeys work in a userform with controls that capture events? for example if you have a textbox and the user hits tab or alt, do you have a chance to intercept that or is it overridden by the host userform?
 
Tried handling KeyDown?
Tab should navigate to the next control in the tab order... why would you mess with that?
I think I'm not understanding the question
 
9:47 PM
@IvenBach yeah even though I basically said it yesterday I'd like to second this
yeah I have KeyDown (and KeyUp) handled but I wasn't tracking what it was doing. like I saw KeyDown fire in textbox1 and then KeyUp in textbox2 so it seemed like textbox1 was reporting the tab to the userform itself.
but I didn't see how I could actually stop or do anything with it in the KeyDown.
with that said that is a good point, there really isn't any reason to intercept a tab. it was more enter than anything since the behavior is not consistent with other windows forms.
I want it to send the click to whichever command button is focused, not tab as it appears to normally.
Or am I misunderstanding the default enter key behavior?
 
Why would you want to circumvent the default tab behavior?
If I were tabbing through a form and then stop on a command I’d find that odd.
 
 
1 hour later…
11:15 PM
@IvenBach i don't want to circumvent the default tab behavior
i just want the enter key to click whichever command button has focus as it does in a normal windows form instead of seemingly do the exact same thing as tab
i guess focus is actually the wrong word specifically but i dont know what else to call it. its the command button that has the double thickness blue highlighting when it is not being directly interacted with.
i called it focus because it is possible for a button to have that while it is the actual focused control if the user is not mousing over it.
 

« first day (2018 days earlier)      last day (38 days later) »