var results = usages.Select(usage =>
new SearchResultItem(usage.ParentNonScoping,
new NavigateCodeEventArgs(usage.QualifiedModuleName, usage.Selection),
GetModuleLine(usage.QualifiedModuleName, usage.Selection.StartLine),
new Selection(1, reference.Selection.StartColumn, 1, reference.Selection.EndColumn).ToZeroBased()));
i should always assume I can guess something from trying myself before asking I suppose
anyways I have a couple actual questions but assume you are still trying to finish what you were working on so I will stop bothering you until you get that done
with the upcoming release, the mocking API is going to ship as an experimental broken feature that can still be played with; there will be blog posts about using it :)
@MathieuGuindon it felt like anything it did I could do myself? I can see it does a lot but it was so overwhelming to look through to tweak. 10k lines or something ridiculous like that.
I could be very wrong, but I see it a bit like XAML styling: you could redefine exactly how any part of any UI element gets to look like -- but then that's a lot of work, so you use a decent-looking framework, and then tweak it to your liking.
yeah not too far from XAML, but then XAML is worlds apart from a UserForm already
without highlighting, a line like If Me Is Ship Then would come up twice - one takes you to the Me, the other takes you to the Ship, but they'd both look identical save for the selection
@theVBE-it'srightforme did you read the tutorials?
tbh I spent more time googling "what is bootstrap" and then "do I have to use bootstrap" and found enough people saying they didnt use it and didnt like it for people learning to justify dumping it
@theVBE-it'srightforme in the same css window you should be able to see the inheritance... i'm sure you already saw that some changes you may do get struck out indicating it's being overriden
it's probably just me but I'm also more inclined to do it Apple's way mainly because I find that the more configurable it is, the more messy it ends up.
> The feature had been broken for some time; this PR restores its functionality.
Also introduces the possibility to highlight (bold, black on yellow) a `Selection` in the search result text of a `SearchResultItem`, and leverages this possibility for _find all references_.
content is obvious, padding separates that from border, border separates from margin, margin is the "force field" so to speak that isolates the box from others
@MathieuGuindon just to double check -- you are adding additional references here but only if hte declaration is a parameter declaration. Does that it mean if I find all references on the object rather than the parameter, it won't include the parameter usages?
as long the result are the same from either location, then that's fine - it's just a bit confusing to see a special case in only one direction, that's all
hm wait no, no if you're on an argument it links to the parameter, and if you're on the parameter it links to both local usages and argument/call sites
Were it, though, I would expect that Find All References would still show "Done!" argument as a reference even when the caret is on the Prompt parameter.
If that's the case already, great! Just not clear from that code I linked since it seems to deal with ParameterDeclaration as a special case
C# short circuits meaning if (a && b) where a evaluates to a false then it will not proceed to evaluate b because with the left operand being false the && can never be true, regardless of what the right operand is.
if (a || b) is the other side. When the left operand a evaluates to true then it doesn't matter what the right operand evaluates to since true || ____ evaluates to true.
Building a truth table on each of the inputs will help illustrate how the operands will result.
> There are multiple pieces in the codebase that need information about the qualifying reference/declaration of a reference, e.g. to determine whether the reference is a member access on the return value of a specific member. Currently, checking this is achieved by navigating the parse tree each time, also taking into account with blocks. This PR moves the qualifier resolution to the BoundExpressionVisitor, which already has all the information present to easily determine the qualifying...
reference. The following qualifier structure has been implemented: - Member accesses are qualified by the reference for their lExpression. - Member accesses return their own reference as the one qualifying a potential access. - For (recursive) default member accesses the innermost access is qualified by the reference of the lExpression and each other access is qualified by the immediately contained one. - For (recursive) default member accesses the outermost access is returned as potentially...
qualifying. - Array accessed are qualified by the reference of their lExpression (potentially with default member accesses in between), i.e. by the reference of the array variable or array returning member. - Array accesses return themselves as potentially qualifying. (To get the array, one has to go up the chain again.) - Index accesses other than array and default member accesses are qualified by the reference of their lExpression. - Index accesses other than array and default member...
accesses return the reference of their lExpression as potentially qualifying. - Dictionary access expressions work like default member access expressions. - Other expressions neither take nor return a reference as (potentially) qualifying. This PR is still WIP; it needs a lot more tests. Moreover, the places currently doing the work manually should be ported to use the qualifying reference, if possible.
The studies show that the eye generally easier picks up dark text on light backgrounds. The thing regarding well-lid surroundings is that it is also hard on the eye to look at a bright screen when it is attuned to a lower light level because of dark surroundings.
However, the effects do not seem to be too significant.
@MathieuGuindon I would like to suggest no background color at all. I think making the reference bold already does the trick and is less distracting.
@MathieuGuindon R# has a move file refactoring. You can access it in the solution explorer's context menu.
@IvenBach I have just started to look at your blog post. Is it possible to change the spacing above headings? I think it looks a bit odd that the space between the heading and its section is larger than the space between the previous section and the heading.
@MathieuGuindon Hi Mat. This is what I was talking about. (I do have a bigger project, not a simple one but this is restricting my workflow a lot)
I click between two modules. You can notice that by seeing the cursor. At the end, I press only the right arrow on the keyboard and it slows immensely, almost freezing the program.
English's funny beast. You'll never hear anybody say anything like "My early husband and I were happily married for 39 years." Who decided that "late" had to be a polite euphemism for having shuffled off the mortal coil?
probably the same person who decided that "having shuffled off this mortal coil" was a polite euphemism for kicked the bucket.
TBH, though, my wife might refer to me as her "early" husband after I'm gone. I despise being late for things, but being late is her hobby, and she's committed to it.
I just got the news, Bobby. Our dear uncle Fred has departed. Where did he go to? He is no longer with us. I know, but where did he go? I'm trying to say that uncle Fred has bought the farm. Oh, can we visit his new farm? No, no. It's not like that. He has kicked the bucket. But I kicked a bucket yesterday. Do I have to go? No, dear, he is pushing daisies. Why can't he pick it up instead of pushing? Because he's six feet under. Under what, mom? Dear, I'm trying to explain that your uncle Fred is now sleeping with the fish.
VBA Rubberducking
VBA Rubberducking