Intro
Multithreading tools exist in Excel - often to run macros in multiple instances of Excel, or to convert macros to vbscripts that can run independently. However I've often come across projects where I'd like to delegate multiple tasks out to async processes, and creating multiple instance...
> @rkapka is correct. However, I recommend merging this after the tests are reworked and doing the quick fix separately. We can re-open the issue manually after it is merged.
> @rkapka is correct. However, I recommend merging this after the tests are reworked and doing the quick fix separately. We can re-open the issue manually after it is merged.
@Mat'sMug I don’t know when I’ll be able to get to it. Worse case I can redo after all major changes are merged. It’d give me more experienc refactoring.
My 5-yo HP Envy still works great for everything I do. My brother has a newer model and his is great too, except we have to keep the touchscreen driver disabled because it locks the system up and thinks it is being touched everywhere.
> If you want to look at the workbook that caused it, there it is. The `MultiThreadTests` module was definitely acting strangely [MultiThreadRubberduck.zip](https://github.com/rubberduck-vba/Rubberduck/files/1636004/MultiThreadRubberduck.zip)
I built my tower 6 or 7 years ago and subsequently added SSDs another HDD, RAM, change the sound card and the graphics card. It really is not hard. The only complicated thing is to connect the internal speaker, power LED, and HDD LED.
I've read stories where people bought 386s or 486s, whatever, but realized it wouldn't fit their old 286 mobos. What to do? Ah, yes, soldering iron!!! :O
There's a reason it's the consensus that shortly after the US civil war was the one time when one person could have triggered a new industrial revolution if they'd traveled back in time.
> I'm closing this pull request and plan resubmit again later. Even though it finds many scenarios of unreachable code, I believe it could use more refactoring/rework to make it easier to understand and review.
And a question: It seems that most (if not all) other inspections seem to 'fit' into a single inspection class/file. So, I tried to do the same with this inspection - and still ended up with two classes/files. To reduce the file/class count, the solution has several supporting Str
> RE: the question - FWIW if you look at Extract Method, there are several files, way more than other refactoring normally needs.
I wouldn't be surprised if we have other inspections where fitting everything in a one file don't make sense. I think that as long we follow the same convention used by refactoring -- creating a folder instead of a file, it should be OK to do that for inspections, too.
@Hosch250 how come rotting PR smells? I’m of a view that PR’s (in general) serves an active/current TODO list out of the “ big fish to fry” picture at least we know which ones are important.
@PeterMTaylor nah, open issues serve as a TODO list - PR's are for "work done and ready to merge", although we sometimes stretch it a bit to "work done and almost ready to merge"
Oo, nice. I think we should use that. We are not using APIs uniformly. We do have user32 and kernel32 but I also have seen private definitions within classes here and there.
@Duga TBH I think that's a case of "if it ain't broke, don't fix it" - I agree with consolidating, but not sure about introducing new dependencies for it
for the call to CreateToolWindow, yes, that class has to be registered for VBE to find it. Beyond that, it shouldn't be needed by anyone else, I think.
I do hope Mat isn't texting and driving. I want him to get home safely.
> By default, the folders are closed. However when searching for a method names, one had to open folders to locate them, which is kind of tedious. It would be nice if CE would save the open/closed state before starting a filter, then during the filter, automatically open all containing folders to reveal the methods/objects matching the filter. Clearing the search should then restore the original open/closed state.
Intro
Multithreading tools exist in Excel - often to run macros in multiple instances of Excel, or to convert macros to vbscripts that can run independently. However I've often come across projects where I'd like to delegate multiple tasks out to async processes, and creating multiple instance...
VBA Rubberducking
VBA Rubberducking