« first day (920 days earlier)      last day (2260 days later) » 
00:00 - 18:0018:00 - 00:00

18:01
[EBrown8534/RubberduckWeb] EBrown8534 pushed commit 251163cb to master: Updated all the "Features" pages to look a little more uniform.
[EBrown8534/RubberduckWeb] EBrown8534 pushed commit 4de6cc53 to master: Blog Feed posts look a little cleaner.
18:14
> The web inspections is triggering a few informational inspections that should probably be disabled for web, because we're the ones providing the VBProject and Module. I've not looked at the web implementation, but I'm assuming it's a matter of configuration.

![image](https://cloud.githubusercontent.com/assets/2716800/21110779/a3141bfe-c06c-11e6-923e-e09a50340ac5.png)
[EBrown8534/RubberduckWeb] EBrown8534 pushed commit 36652b8e to master: Cleaned up "Inspections" and the results from it substantially, made it slightly more user friendly.
> We'd have to cherry-pick inspection results' Target.DeclarationType and filter out DeclarationType.Project and DeclarationType.ProceduralModule to get these ones out of the way without outright disabling that inspection.
> I'm just getting started, but this at least standardizes some of the pages to be a little more uniform and less ugly.
@Duga @Mat'sMug You want to assign me to some of the issues on RDWeb?
I think you can assign yourself to whichever you feel like implementing
Alright, I'll grab one or two of them here quick.
> Ahh. Not as simple as I thought. Cloning now.
> Do we want to self-author this in the current website (/Blog) or use a separate piece of software for it?
> FWIW I'm not going to be renewing the original rubberduck-vba.com domain when it expires in February.
> The results are currently of type ICodeInspectionResult, how trivial would it be to get the Target.DeclarationType from that?
@Mat'sMug Is it trivial to build previous versions of RubberDuck?
18:25
I guess.... but why would you want to do that?
2.0 is beta right now, correct?
So why don't we add a dropdown to Inspections for 1.x (Stable) and 2.x (Beta)?
because the 1.x parser will choke on half the code you give it
Why? What's different between them?
18:26
uhm, a full rewrite?
Ah, alright then.
Also, how can we get that Target.DeclarationType from ICodeInspectionResult?
(I know nothing of Rubberduck to be fair.)
gah, you got me there.. the Target is a member of the base abstract class, InspectionResultBase. that's rather annoying.
all results can be safely cast to the base type though
IInspection specifies it:
IEnumerable<InspectionResultBase> GetInspectionResults();
basically ICodeInspectionResult is probably redundant
It's a piece of cake then.
Also, added another PR. Not sure if you want to merge it or not.
@Mat'sMug Target is null for inspections.
all of 'em?
What do you need the target for?
18:35
Checking that now.
Aha, not all of them.
depends on the inspection type - some results are instantiated with a ParserRuleContext, others with a Declaration (the Target)
Think I have the fix for that.
Whoop whoop. Fixed. :)
Also added a "No issues were found" if no inspection results are identified.
huh, pretty that was there already. IIRC it even said "congratulations, Rubberduck couldn't find any issues in your code"
or something like that
Not in the website.
I think I like "no issues were found" better though
18:40
Boom, committing and closing.
You want to merge that other PR I have or should I?
taking a look
@Duga interesting
> @ckuhn203 Alright, but I just fixed it, committing to my fork then adding PR...;)
Lmao Apparently he and I are going to be competing to fix this stuff. Lol
18:42
[rubberduck-vba/RubberduckWeb] EBrown8534 pushed commit 6cca6ffe to master: Standardized copyright with general web style.
[rubberduck-vba/RubberduckWeb] EBrown8534 pushed commit 251163cb to master: Updated all the "Features" pages to look a little more uniform.
[rubberduck-vba/RubberduckWeb] EBrown8534 pushed commit 4de6cc53 to master: Blog Feed posts look a little cleaner.
[rubberduck-vba/RubberduckWeb] EBrown8534 pushed commit 36652b8e to master: Cleaned up "Inspections" and the results from it substantially, made it slightly more user friendly.
@Duga I commit a lot...lol
Merge pull request #19 from EBrown8534/master

Standardized some of the pages
@Mat'sMug One of the inspections has a capitalization issue:
> variable 'foo' is not used
But all the other issues are:
> We provide the project & module, so it's a bit confusing for a user to get inspection results for bad names outside of their control. It's kind of a dirty hack to use the names, but works well enough.
> Variable 'foo' is used but not assigned
18:46
hmm probably because the word "variable" is itself taken from a ressource and the string is reused for "procedure 'DoSomething' is not used"
it's a tought problem: we can't capitalize "variable" in the resources because it's often used in the middle of a sentence, and we can't capitalize the first character of the inspection result description because we don't know what language it is and whether a capital first letter even means anything
Why does it show for the other inspection as capitalized though?
probably because "Variable" is part of that inspection's resource string. a procedure isn't "used but not assigned" ;-)
> ...let's see which dirty hack is the cleanest :racehorse:
> @ckuhn203 It's all good, if you don't mind merge the PR you made and I'll move that code to the view to line up better with MVC's style, I also fixed another issue in my fix (which I haven't PR'd yet) which is "No issues were found" should display when no inspection results are returned.

Likewise, are we sure we don't want to use the method @retailcoder suggested? It's quite trivial:

var results = Model.Where(o => ((InspectionResultBase)o).Target != null && ((InspectionResult
> @ckuhn203 It's all good, if you don't mind merge the PR you made and I'll move that code to the view to line up better with MVC's style, I also fixed another issue in my fix (which I haven't PR'd yet) which is "No issues were found" should display when no inspection results are returned.

Likewise, are we sure we don't want to use the method @retailcoder suggested? It's quite trivial:

var results = Model.Where(o => ((InspectionResultBase)o).Target != null && ((InspectionResult
18:52
Aha, @Duga has a bug.
> @EBrown8534 that might remove inspection results where Target is null though; I like @ckuhn203's solution, which hardwires the actual inspection type. After all, we are looking at one specific inspection.
merged
[rubberduck-vba/RubberduckWeb] Unrecognized author pushed commit e072c053 to master
2
Strip out Module & Project naming suggestions

We provide the project & module, so it's a bit confusing for a user to get inspection results for bad names outside of their control. It's kind of a dirty hack to use the names, but works well enough.
Merge pull request #20 from ckuhn203/master

Strip out Module & Project naming suggestions Fixes #18
@Mat'sMug I'll update my version to use his solution and then fix the "No issues were found" thing.
@Duga lol, it's been too long has it?
3
@EBrown perfect!
18:55
@Mat'sMug How do I update my GitHub fork to pull the stuff you merged?
PR from RubberduckWeb to your fork
hi @RubberDuck!
@RubberDuck I'm going to slightly alter your solution, but I won't take your fix away. :)
No worries mate. Just figured I'd fix it since I raised it.
If you've got a better way, I'm all about it.
My method wasn't better, other than where we were going to put it, but even that's arguable.
I'm going to just add a quick feature, so that if no inspections are found it will display "No issues were found"
2
18:58
My first thought was to change the vbe builder to make it not trigger to begin with, but then I realized it was in a dependency and the method wasn't virtual and...
I'm at work, so quick hack it was.
Yeah, I think you saw my solution, no?
@RubberDuck it's ok, I'll add a note about it in the builder, so we don't change the project/module names
@EBrown no, link?
Merge pull request #17 from EBrown8534/master

Fixed all the packages
Merge pull request #19 from EBrown8534/master

Standardized some of the pages
[EBrown8534/RubberduckWeb] Unrecognized author pushed commit e072c053 to master
18:59
@RubberDuck It's in the issue @Mat'sMug closed.
Strip out Module & Project naming suggestions

We provide the project & module, so it's a bit confusing for a user to get inspection results for bad names outside of their control. It's kind of a dirty hack to use the names, but works well enough.
Merge pull request #20 from ckuhn203/master

Strip out Module & Project naming suggestions Fixes #18
Merge pull request #1 from rubberduck-vba/master

Merge from RDWeb Base
@EBrown eh, it closed itself!
@Mat'sMug Mhmm. ;)
"Fixes #18" in the commit message did it
19:01
GitHub is magic :)
4
Yeah and now I can't do a pull...lol
@Mat'sMug lol. I think it picked up my work email... oops.
Re inspection capitalization, resource strings, and internationalization, I use something like this all the time:
public static string Captialize(this string input)
{
    var tokens = input.Split(new[] {' '}, StringSplitOptions.RemoveEmptyEntries);
    if (tokens.Length == 0)
    {
        return input;
    }
    tokens[0] = CultureInfo.CurrentCulture.TextInfo.ToTitleCase(tokens[0]);
    return string.Join(" ", tokens);
}
"See the output window for details" there are no details.
THERE ARE NOT UNCOMMITTED CHANGES
@Comintern huh, we want that
19:06
Good thing I wasn't actually working on anything, just gonna delete that whole project from this PC.
> Are the inspections running with the default settings? Wouldn't it be easier to just set the severity to "Ignore"?
> @comintern they are. But that would disable the inspection altogether, not just filter out the specific results about the test module / test method names.
@Mat'sMug I see how the original "No Inspection Results Found" thing worked, @RubberDuck fixed it with his hack, no need for me to do anything there. ;)
> @comintern that would disable all of the UseMeaningfulName inspections, so we would miss bad variable names.
Ehh yes there is, so ugly.
@EBrown I didn't even mean to. lol
19:10
@RubberDuck Totally accidental on your part. Lol
@RubberDuck @Mat'sMug @Hosch250 If you all don't mind, I'm going to change how errors are display on Inspections as well. (If you enter invalid code, etc.)
@EBrown Sure.
whatever works and looks pretty :)
[EBrown8534/RubberduckWeb] EBrown8534 pushed commit da765287 to master: Replaced how we display the fact that no issues were found in inspections with a more clean solution. (Follows the design more tightly, and eliminates a view.)
@Mat'sMug That's the kicker: "looks pretty." ;)
@EBrown that's the best kind of bug fix IMO.
19:28
@RubberDuck Feel free to read the messages I posted above about altering the MVC structure and adjusting the design a bit and let me know what you think of any/all of them. It's your project too.
19:51
Should indenting trigger a reparse? The token locations in the parse tree are wrong for lines that get indented.
then yes :)
maybe it could do a reparse only, without needing to resolve?
@EBrown IMO the controller should be doing the filtering & ordering, not the view. At least, unless you're allowing the client to filter & sort with some js.
Also, it's so not my project anymore.
Oh, yeah. It busts all the quick-fixes if you already have inspection results.
That's my first commit in a year...
19:55
@RubberDuck this forces you to have a beefy-ish server though.
and if we go for "getting inspection results as some kind of JSON", we might as well filter on client-side
@Vogel612 the server's doing the work anyway, its in the razor.
But yeah, you're right.
erghh, dat naming
0
Q: VBA Code optimizing

ChiragI have the below code, but is very slow. Is there a way to improve it? I'm a beginner with VBA and would appreciate your help. What it does is it goes through a table and looks up in each worksheet for criteria to match and give values accordingly. Criteria differ by line in the initial range: S...

@ThunderFrame - That was a good test for bracketed identifiers inside string literals. Cells(CEllrow, TC + 5) = "=[@[Actual Rebate $ for Line]]-[@[Committed - Rebate]]". :shudders:
Argh! You have GoTo statements within your If statements which lead into other legs of the If statement! — YowE3K 14 mins ago
lol
20:11
The fun one is GoTo Filler: in the ElseIf leg that leads to the If leg. Ummm... can I lend you an Or keyword?
@Comintern string literal content shouldn't have any impact.
It was a problem in the indenter - the fix for chat.stackexchange.com/transcript/message/33933348#33933348 was to escape bracketed expressions and string literals at the same time.
21:22
> It was a long time ago, but was thinking of just migrating the wordpress.com blog to a self hosted Wordpress site at blog.rubberduckvba.com. Honestly, probably not ever going to be a big deal.
21:41
Rubberduck's indenter basically is Smart Indenter for VBA - it's just a C# port of the original VB6 codebase (with additional bug fixes and 64bit support). — Comintern 10 mins ago
"just a C# port" ...and a massive refactor/despaghettification
@Mat'sMug Didn't say how the additional bugs got fixed... :-)
22:07
@Comintern perhaps we should have an "indent your code here" box on the indenter page?
That shouldn't be difficult - It'd basically be like the sample code in the settings window.
I should really get VS2015 installed at home.
22:24
WTF?
?[Concatenate("","]")]
Error 2015)]
That error is so last year.
2
how the hell does it include ")]" in the result?
That's a damn good question. It almost looks like whatever is throwing is crashing a buffer somewhere.
last year was an overflow?
?[Concatenate("","]")] This can be pretty much anything...
Error 2015)] This can be pretty much anything...
Got it. It's Debug.Print just appending anything after a single ":
?" Foo
 Foo
?[[Concatenate("","]")]
Error 2015
?[Concatenate("","]
Error 2015
?[Concatenate("","]        "This gets appended.
Error 2015This gets appended.
22:44
huh, in a procedure block it gets converted
Debug.Print [Concatenate("","]; ")]"
I'm betting the parser/indenter can't handle that?
Unsure. The VBA parser can't handle it, so I can't really check:
If [Concatenate("","]")] <> vbnullstring Then '<--Expected Then or Goto
Debug.Print [Concatenate("","]; " : Beep : 'Not a comment)]" 'Is a " comment
This is a parse error, but VBA handles it fine:
Sub foo()
If True Then
Debug.Print [Concatenate("","]; ")]"
End If
End Sub
Sub foo()
    If True Then
        Debug.Print [Concatenate("","]; ")]"
    End If
End Sub
Indents fine though.
@ThunderFrame I get a resolver error on that one.
@comintern - yep, I suspect it thinks the comment starts at the first '
Probably.
23:09
And... Out of Memory in VBE
blames square brackets
and BOOM
23:36
> I think I can do this tomorrow. There are only two places where the DebugDeclarations are injected, ParserState and MockParserState. So extracting the SpecialFormsDeclarations into their own class and injecting that as well should be easy.
@Duga Does MDoerner know we're here?
23:49
I think not. We should invite him.. but if he doesn't have the CR rep (20) I won't be able to grant him explicit wrire access until later tonight (it's 6h50pm, heading home)
Room owners are supposed to be able to grant that, I think, but it doesn't work.
<driving>
00:00 - 18:0018:00 - 00:00

« first day (920 days earlier)      last day (2260 days later) »