I think the issue is not the number of results. It rather looks like there is a race condition in the rendering engine we stumbled upon when adding the scroll viewer.
TBH, we do something that really is not intended. On the grouping grid, we both have grouping and virtualization enabled. This is not a supported scenario for datagrid. Using groupings usually disables virtualization.
The main problem debugging this is that I have never been able to reproduce the issue.
> @joyfullservice Thank you very much for the link to your repo. I am finally able to reproduce the issue. So, I am finally be able try to figure out what is really going on.
Don't laugh, but, from time to time, my friends and I host a multiple-course KFC dinner, and I have a spreadsheet to optimise the order. This is to make sure we order the right combination of 'bucket'-type items (i.e. SKUs that contain multiple pieces, often of different types):
to minimise lef...
Looking at the memory at hex(objptr(Application.VBE.ActiveVBProject)) - lots of interesting pointers, but I have no idea what they represent. Most of the VB6 structs have been decoded, but I can't find anything for VBA...
aside from that convo... everyone holding up? haven't talked to many of you in a month or so? about to jump on a call for the next 2 hours, but will check back after
IDK if that's a good idea. you'd be doing lot of pointer chasing and VBA make it really hard to do any pointer chasing, especially beyond the first pointer.
right now, CE uses Declarations which is OK. What we really need is something like mutable Declaration so that CE can create Declarations from TypeLib API + ComProject, and when parsing finishes, to update? upsert? the data.
@Cyril still really dislike WFH full time. Once I can find an open furniture store, I'll be buying a new desk & chair. I've got an old office desk from the days when typewriters ruled the world and what was a nice desk chair. The chair is failing and it just doesn't fit the desk very well. A day at a time is tolerable. After weeks on end, everything is sore from sitting here 8 hours a day.
it's true that VBE doesn't do away with the windows when closed but it doesn't mean that we have to have it hot if it's closed. We still control the WPF and thus can disable that.
> This PR is another stab at resolving issue #5442 Not swallowing that event in the test explorer made the sample project provided in the issue stop freezing for me. (In PR #5482, it had already been removed from the inspection results window, but not from the test explorer as it had been added in a different PR than the one introducing the issue, probably a later one.) I hope this change also works for other people. Once we know that it really works in the field, we might reintroduce a...
handler, but using a better scheme than swallowing the event to handle the original problem for which the handler has been added.
> # [Codecov](https://codecov.io/gh/rubberduck-vba/Rubberduck/pull/5506?src=pr&el=h1) Report > Merging [#5506](https://codecov.io/gh/rubberduck-vba/Rubberduck/pull/5506?src=pr&el=desc) into [next](https://codecov.io/gh/rubberduck-vba/Rubberduck/commit/65bf91efc6f24fb872c6f09cea7bcdec017d846c&el=desc) will **decrease** coverage by `0.00%`. > The diff coverage is `n/a`.
@FreeMan i completely hear you... i've been using a nightstand to hold both monitors (stacked upon the laptop and docking station)with a lawnchair to sit in (i'm on chair #2 after the first one died)
even if not ideal, at least it's work... i have a few friends who are going out of head and mind with nothing that entertains them consistently for 3 months
even if not ideal, at least it's work... i have a few friends who are going out of head and mind with nothing that entertains them consistently for 3 months
> The PR above resolved the issue for me using the linked Access database. However, I am not fully sure this fixes the problem completely since I did not experience the issue with other projects. So I would be grateful if others experiencing this issue could test whether the latest pre-release actually fixes it.
> Hopefully I will be able to test this ASAP before Monday. Thanks a lot and have an amazing COVID free week end :-)
Envoyé de mon cerveau et d’un doigt... Savoir Ubilogia www.ubilogia.com 514-991-3438 ________________________________ De : Max Dörner <notifications@github.com> Envoyé : Friday, May 29, 2020 3:35:28 PM À : rubberduck-vba/Rubberduck <Rubberduck@noreply.github.com> Cc : Georges VIVIER <gvivier@ubilogia.com>; Mention <mention@noreply.github.com> Objet : Re: [rubberduck-vba/Rubberduc
> Hopefully I will be able to test this ASAP before Monday. Thanks a lot and have an amazing COVID free week end :-)
ubidev ________________________________ De : Max Dörner <notifications@github.com> Envoyé : Friday, May 29, 2020 3:35:28 PM À : rubberduck-vba/Rubberduck <Rubberduck@noreply.github.com> Cc : Georges VIVIER <gvivier@ubilogia.com>; Mention <mention@noreply.github.com> Objet : Re: [rubberduck-vba/Rubberduck] MS ACCESS and VBE hung with heavy CPU\MEM use after parse (#5442)
I just had some WTF while trying to do a unit test. Kept giving me object or with not set stuff on my asserts. The problem magically went away when I did a parse....
So question is: Shouldn't the run test check if the parse is dirty and tell you to parse before running your tests?
We’ve seen how to leverage the default instance of a class module to define a stateless interface that’s perfect for a factory method. At the right abstraction level, most objects will not require more than just a few parameters. Often, parameters are related and can be abstracted/regrouped into their own object. Sometimes that makes things… Continue reading Builder Walkthroug…
> After a quick validation using release Rubberduck v2.5.0.5457-pre, I can confirm that on my side, the frozen state has dissapeared and the plugin seems to work as it does not freeze at the end of all inspections. I'll will work more with the tool during the coming week!