VBA Rubberducking

Duga

12:01 AM

RELOAD!

[banane-io/PDB] 1 opened issue. 17 issue comments.

[retailcoder/Rubberduck] 49 commits. 36109 additions. 19189 deletions.

[rubberduck-vba/Rubberduck] 5 opened issues. 1 closed issue. 13 issue comments.

[rubberduck-vba/RubberduckWeb] 2 opened issues. 3 issue comments.

IvenBach

Thanks for the duck help earlier.

Duga

[Zomis/flexgame-server] 8 commits. 3 opened issues. 1 issue comment. 804 additions. 44 deletions.

IvenBach

Home Time.

Duga

[Zomis/Monopoly] 4 commits. 183 additions. 6 deletions.

Mat's Mug

Wow, Excel actually crashed on me trying to experiment with this. — Mat's Mug 12 secs ago

ThunderFrame

1:16 AM

> property procedures always take their arguments ByVal

^ WTF?

Duga

[rubberduck-vba/Rubberduck] Vogel612 commented on issue #3485: Inspections should be sorted in the inspection settings

> additional simplification possibility: make the grid filterable?

Mat's Mug

@ThunderFrame IKR?

Public Property Let Foo(ByRef values As Variant)
    Debug.Print "Foo: " & VarPtr(values)
End Property

Public Sub Test()
    Dim values(0 To 1) As Long
    values(0) = 1
    values(1) = 2

    Dim v As Variant
    v = values

    Debug.Print "Test: " & VarPtr(v)
    IllegalByRefArray v
End Sub

Private Sub IllegalByRefArray(ByRef values As Variant)
    Debug.Print "IllegalByRefArray: " & VarPtr(values)
    Foo = values
End Sub

and yet... ^^^^ gets you a different VarPtr value for the 3rd one

ThunderFrame

this works

Sub Bar(j() As Integer)
    Dim k() As Integer
    k = j
    Module1.Dummy = k
End Sub

Mat's Mug

TBH there's way too much fluff in OP's code, it's hard to follow

ThunderFrame

I think the point he is making is he can pass an array directly to the property, but can't pass an array via a procedure to the property.

Mat's Mug

1:19 AM

I think the point VBA is trying to make is that you shouldn't be doing that

FFS encapsulate your array and expose an indexed property

ThunderFrame

but making a copy of the array in the procedure, and then passing that to the property, does work.

Mat's Mug

yup. and it's a different VarPtr too

ThunderFrame

yeah, just checked - looks like the property argument is byval

Mat's Mug

we need an inspection for that

ByRef on Property Let / Property Set value parameter is misleading

and implicit modifier is outright confusing, given the implicit modifier is ByRef everywhere else in VBA

ThunderFrame

well, en explicit byval on an array argument is a syntax error

Mat's Mug

1:27 AM

ergo, don't do that

pass a Variant, or expose the array through an indexed property

ThunderFrame

^^

So what's VBA doing - special hack for an array being passed to a property let, and error 51 for a ByRef array being passed to a property let?

Mat's Mug

I don't get error 51

I get a hard crash

ThunderFrame

that must make testing fun

errea 51

Mat's Mug

lol

answer posted

> A ByRef modifier on a Property Let mutator makes no sense: it's a blatant lie (it's not passed by reference!) and makes your code very confusing. Don't stick a ByRef modifier on a Property Let value parameter just to satisfy the syntax that otherwise refuses to pass an array - you're twisting VBA's arm, jeopardizing your users' unsaved work, and making your code tell lies.

Pass a Variant instead, or properly encapsulate your array through an indexed property. Anything else is just a dirty stinking hack.

this

and that's why I'm ambivalent about arrays or UDTs in general; VBA doesn't make it easy to work with those without having to know too much about either and I don't like wrapping them into variants. "Hey, please waste more bytes & instruction cycles because efficiency is evil."

Duga

1:51 AM

[rubberduck-vba/Rubberduck] retailcoder added label feature-inspections to issue #3486: Inspection for misleading ByRef (implicit or explicit) modifier in property mutator

[rubberduck-vba/Rubberduck] retailcoder added label enhancement to issue #3486: Inspection for misleading ByRef (implicit or explicit) modifier in property mutator

[rubberduck-vba/Rubberduck] retailcoder added label up-for-grabs to issue #3486: Inspection for misleading ByRef (implicit or explicit) modifier in property mutator

[rubberduck-vba/Rubberduck] retailcoder added label hacktoberfest to issue #3486: Inspection for misleading ByRef (implicit or explicit) modifier in property mutator

[rubberduck-vba/Rubberduck] retailcoder milestoned issue #3486: Inspection for misleading ByRef (implicit or explicit) modifier in property mutator

[rubberduck-vba/Rubberduck] retailcoder added label difficulty-02-ducky to issue #3486: Inspection for misleading ByRef (implicit or explicit) modifier in property mutator

[rubberduck-vba/Rubberduck] retailcoder opened issue #3486: Inspection for misleading ByRef (implicit or explicit) modifier in property mutator

> https://stackoverflow.com/q/39872663/1188513

`Property Let` and `Property Set` value parameters are passed by value, regardless of what the modifier says.

In other words, a parameter in VBA is implicitly passed `ByRef`, *unless it's the value parameter of a property mutator procedure*, in which case it's always passed `ByVal`.

This is thoroughly confusing, because it makes this code be a lie:

Public Property Let Foo(ByRef value As Long) ' passed ByVal anyway!
End Property

[rubberduck-vba/Rubberduck] retailcoder commented on issue #3486: Inspection for misleading ByRef (implicit or explicit) modifier in property mutator

> Also worth noting, that if the parameter is an array, there's a non-zero chance that the user's code can completely crash the host process, or throw run-time error 51 / *Internal error*.

If the parameter is an array, user should either pass the parameter as a `Variant`, properly encapsulate the array and expose an indexed property for it, or discard the property and outright expose the array as a public field.

this

2:54 AM

Thought I'd ask just in case. Does anyone know if there's a documentation that explicitly indicates that a UDT cannot contain dynamically sized array / string that is also pinned to the UDT's structure (IOW, changing the member's dimension also changes the UDT's size)? So far, it doesn't seem to me the language allows for that type of structure but wanted to confirm that was the case.

Mat's Mug

hmm, no idea

IvenBach

3:20 AM

@Mat'sMug You able to help me connect my VS with GH?

Mat's Mug

I'm heading out :-/

IvenBach

@this Based on my supremely minimal testing I always had it be the same size. 4byte pointer to a string didn't change when I changed the strings length.

@Mat'sMug Tomorrow or weekend?

Mat's Mug

yeah

IvenBach

I'll ping you tomorrow.

SlowLearner

3:52 AM

Hey have you guys ever seen / heard of the files WINWORD.box and EXCEL.box?

My EXCEL.box file was corrupt and preventing me from opening any xl file with a userform in it...

Thought it might be of interest for RD:
- https://answers.microsoft.com/en-us/surface/forum/surfpro4-surfoffice/office-2016-crashes-when-userform-added-to-vba/f2f16ffa-9a1f-4bfd-babb-1e93a78d5c65 (see mid of pg 2 for solution)
- https://windowssecrets.com/forums/showthread.php/32615-Winword-box-(Word-2000-SR1)?s=17cf34d36d89f56264a1066ee52b6b16&p=167660&viewfull=1#post167660 (more info)

I've verified that deleting the .BOX file from my profile allowed userforms to work again, TL;DR apparently the issue is with custom toolbox layout becoming corrupted.

@Mat'sMug @ThunderFrame ^^

Duga

[rubberduck-vba/Rubberduck] qin-yin starred us

3

SlowLearner

lol - of course reinstalling windows can fix (almost) anything: excelforum.com/excel-programming-vba-macros/…

ThunderFrame

4:08 AM

@SlowLearner but not pcworld.com/article/2948092/security/…

SlowLearner

but... there's absolutely no excuse for reusing a motherboard when reinstalling an OS - they deserve what they get ;-)

(even MS knows this, they will xFer OEM licence if you replace MB with like for like)...

BUT... $H!7 - I bought 2 MBs from the US last month to replace my dead Dell MB...

ThunderFrame

@SlowLearner you can't even trust the shipping company -extremetech.com/computing/…

SlowLearner

4:27 AM

I've always known that I'm not smart enough to be dishonest, TIL another reason why!

Duga

[retailcoder/Rubberduck] retailcoder pushed commit 2f4d8fa6 to attributes: fixed IoC config for QuickFix

[retailcoder/Rubberduck] retailcoder pushed commit 75e1f9f7 to attributes: PredeclaredId works!

Duga

5:05 AM

[rubberduck-vba/Rubberduck] Imh0t3b opened issue #3487: Duration of tool tips shown is too short if with text is long

> E.g. in Settings -> Code Inspection Settings -> Late Bound WorksheetFunction Call the tool tip is hard to read as it disappears far to soon. Duration should be infinite or depend on text length (x-times word count?).

Additional I made some translations (German) with the TranslationHelper, but I have no Visual Studio installed to fork. How should I contribute my translations?

[rubberduck-vba/Rubberduck] Imh0t3b edited issue #3487: Duration of tool tips shown is too short if text is long

[rubberduck-vba/Rubberduck] Imh0t3b edited issue #3487: Duration of tool tips shown is too short if text contains more words

Duga

5:19 AM

[rubberduck-vba/Rubberduck] Imh0t3b edited issue #3487: Duration of tool tips shown is too short if text contains more words

Duga

5:44 AM

[rubberduck-vba/Rubberduck] Imh0t3b forked us into Imh0t3b/Rubberduck

M.Doerner

8:02 AM

@this The VBA specification explicitly allows resizable arrays in UDTs.

ThunderFrame

@ThunderFrame it's in the language specification: "If the <value-param> of a <property-LHS-declaration> does not have a <parameter-mechanism> element or has a <parameter-mechanism> consisting of the keyword ByRef, it has the same meaning as if it instead had a <parameter-mechanism> element consisting of the keyword ByVal." — Rory 34 mins ago

M.Doerner

At the bottom of paragraph 5.2.3.3.

ThunderFrame

@M.Doerner do you just do that with Redim?

M.Doerner

I don't know. Maybe it works with ReDim, maybe you have to assign an array.

I never tried.

Why would one put something like this into the specification? I think the inspections should be called Implicit ByVal inspection.

Duga

8:53 AM

[rubberduck-vba/Rubberduck] pierro42 starred us

4

ThunderFrame

@M.Doerner except using ByRef is a lie - does ByRef also trigger the implicit ByVal inspection?

M.Doerner

I think it should since this would also be implicitly ByVal.

Duga

9:46 AM

[rubberduck-vba/Rubberduck] Vogel612 added label user-interface to issue #3487: Duration of tool tips shown is too short if text contains more words

[rubberduck-vba/Rubberduck] Vogel612 added label difficulty-01-duckling to issue #3487: Duration of tool tips shown is too short if text contains more words

[rubberduck-vba/Rubberduck] Vogel612 added label enhancement to issue #3487: Duration of tool tips shown is too short if text contains more words

[rubberduck-vba/Rubberduck] Vogel612 added label good first issue to issue #3487: Duration of tool tips shown is too short if text contains more words

[rubberduck-vba/Rubberduck] Vogel612 added label up-for-grabs to issue #3487: Duration of tool tips shown is too short if text contains more words

[rubberduck-vba/Rubberduck] Vogel612 added label hacktoberfest to issue #3487: Duration of tool tips shown is too short if text contains more words

[rubberduck-vba/Rubberduck] Vogel612 commented on issue #3487: Duration of tool tips shown is too short if text contains more words

> Re the translations: You don't need Visual Studio to fork. I can see you already do have a fork, the next step is creating a "working copy" of your fork. For that, look to the "top" right on https://github.com/Imh0t3b/Rubberduck above the listing of files. There's a green button "clone or download".

Use that to create a working copy (read up about git if you have problems in this step).

Then put your changes into that working copy, commit and push them to your fork and open a PR. Do not

QHarr

10:12 AM

Hi, i did the recent update and now Excel keeps crashing initially just when trying to close the file but now also on opening an existing file. No problems with creating a new workbook. I can't see this in the recent issues on GitHub, is this happening for others please? I am using 64 bit Excel 2016 install.

By update i mean installed the latest RubberDuck

this

@M.Doerner Unfortunately it doesn't address the question of whether it can be pinned to the array or not. Defining a UDT that contains a single member non-fixed-length string or array without bounds will come out with LenB(thisUDT) => 4 (on a 32-bit arch). In contrast, if I defined a UDT with a member like thisMember As String * 10 or thisMember As Byte(19), those get pinned to the UDT, so LenB(thisUDT) => 20 (again on 32-bit arch).

AFAICT, there is no way to have a dynamically sized member that's also pinned to the UDT's structure.

M.Doerner

Crash on exit can still happen, but should actually happen less often than before; probably you are one of the unlucky ones for which it crashes now. We are still investigating this, but it is rather tedious since the exceptions get thrown after we have shut down Rubberduck.

Crash on open is something new. That should not happen at all.

@QHarr Did you uninstall the previous Rubberduck before installing the latest release?

QHarr

The crash on open may be related to another factor as it seems to be only files from a specific directory that it is happening with at present. I did not do an uninstall. My bad? Was it a requirement i go to the relevant directory and manually delete all files?

ThunderFrame

@this IKR - it would be useful when using CopyMemory and reading binary, to be have a dynamically sized UDT, but I don't think it can be done

I've always had to use at least one UDT and a dedicated variable to read variable length binary

M.Doerner

11:31 AM

@QHarr I hope the installer uninstalls previous versions, but I am not too sure. There have been problems in the past as far as I understand from @Mat'sMug.

A spacific directory? That is interesting. Would you be able to share the filename including the path? If you can't, no problem.

Mat's Mug

@M.Doerner I brought in the CW / Ninject-removal into my 'attributes' branch, and noticed most inspections wouldn't be loaded, and quickfixes too. See earlier ping - not sure if that's the right way to do this, but it works (I should be making a PR out of that branch some time this weekend)

As for the installer.. I think it's safer to uninstall first, but maybe it's just me being paranoid about stale registry keys

The single most annoying thing IMO is that the settings don't seem to keep up with a newer install, and you basically need to wipe the file to get new inspections to show up in the settings dialog

QHarr

11:54 AM

@M.Doerner Specific network location at my work place. Not sure if have understood correctly but is as follows:

R:\AAAAaaaaaaaaaa\BBB Bbbbbbbbbcbcc\CCCCCCCCCCCC CCCCCC\23_DDDDDDDDDD RETURNS TEAM\Development\Eeeeee\Ffff\Mmmmmmm\BBB

Where i have matched the length and upper lower case and any symbols numbers

Filename is Cccccc Dashboard - CCC June 2017_20170929.xlsb

Duga

1:03 PM

[rubberduck-vba/Rubberduck] R0xtar opened issue #3488: User Rubberduck only for versioning ?

> Hello,

Firstly let me thank you all for this amazing OSS project. I'm pretty new to Access VBA development (3 weeks) and my main task is to version our Access source code.

I have some issues with code inspections etc (endless loading and memory leak on startup) that freezes my Access 2013 project (tried many solutions and workarounds found in previous issues but didn't find a way make things work). Actually, I don't need code inspectons and others IDE features... So my question is : is i

Moacir

Dim info As Worksheet
Set info = ThisWorkbook.Sheets("Info")
Dim meses As Variant
Dim rng As Range
rng = Range(info.Cells(1, 1), info.Cells(12, 2))
meses = rng.Value

Its giving me an error when I try to set the range

What am I not seeing?

If it matters, this code executes on a worksheet_change event

Mat's Mug

@Moacir the inspection result for 'object assignment without Set keyword'? ;-)

Duga

1:21 PM

[rubberduck-vba/Rubberduck] Vogel612 added label enhancement to issue #3488: User Rubberduck only for versioning ?

[rubberduck-vba/Rubberduck] Vogel612 added label feature-source-control to issue #3488: User Rubberduck only for versioning ?

[rubberduck-vba/Rubberduck] Vogel612 added label support to issue #3488: User Rubberduck only for versioning ?

Moacir

@Mat'sMug Yas

Thanks

Duga

[rubberduck-vba/Rubberduck] Vogel612 added label discussion to issue #3488: User Rubberduck only for versioning ?

Mat's Mug

> No, that is not possible. And frankly, if you don't need the navigation enhancements or any other feature, then you don't need source control either.

Feel free to fork the project and butcher it until all that's left is source control, I'm not doing that.

^ oh the self-restraint here

Vogel612

hmm ... I should've just slapped a status-declined on it then, eh?

this

Not exactly the best way to win stars, @Mat'sMug. Besides, this wouldn't be an issue if there was the memory leaks & crashing.

Mat's Mug

1:28 PM

@this hence why I didn't put it in the issue ;-)

but I take offense with "I don't need any of whatever you've been working on for the past 3 years, thanks for this awesome project"

Vogel612

pretty understandable...

this

I hear you.

Mat's Mug

tempted to ask for his SO profile, and spam every single VBA question of his with "oh BTW, Rubberduck's inspections would have caught that"

Duga

[rubberduck-vba/Rubberduck] Vogel612 commented on issue #3488: User Rubberduck only for versioning ?

> Hey there,

a few points:

1. Source Control is considered an experimental feature. We don't consider it ready for full use yet.
2. Source Control is but a small part of what Rubberduck intends to achieve. While it may be useful to have the notion of "I only want Source Control" it's not a notion that's conform with the vision of what Rubberduck wants to be.
3. No... We don't want to throw away three years of work by making it easy to ignore when Rubberduck is bugging you about the mista

[rubberduck-vba/Rubberduck] Vogel612 closed issue #3488: User Rubberduck only for versioning ?

[rubberduck-vba/Rubberduck] Vogel612 added label status-declined to issue #3488: User Rubberduck only for versioning ?

Mat's Mug

thanks @Vogel612, well put :)

Vogel612

1:36 PM

pleasure.

not so much a pleasure like my damn screen failing on me,...

Hosch250

@Vogel612 Ever see my question about what is the difference between F# and Haskell type systems?

Vogel612

um... no

Hosch250

Oh.

Vogel612

linkey? (also brb coffee)

Hosch250

It was a couple days ago.

yesterday, by Hosch250

@Vogel612 What do you mean by "proper type checking"?

Vogel612

1:41 PM

@Hosch250 ahh ... that was in comparison to something like LISP

Hosch250

Oh. How does Lisp do it?

Vogel612

not meant in comparison to F#, though I see how it's misunderstandable...

Hosch250

I just know F# and JS.

Vogel612

LISP has only a single type: a 2-tuple

Hosch250

I finally understand the parentheses.

Vogel612

1:43 PM

well that's a massive simplification, but

Hosch250

Does it have ints and strings?

Vogel612

in the end it boils down to that you can express every LISP type as a tuple of a scalar and pointers.

Hosch250

Oh, it works with pointers. Fun.

Yeah, that makes sense.

Because really, function-currying is kind of like that.

You have a function and an argument.

The argument may be data, or it may be another function that takes an argument, or anything.

(or it may be None)

Vogel612

interestingly it's a very simplistic way to enable mark-sweep garbage collection

> Types can overlap, and objects can belong to two or more types. Consequently, we can ask whether an object belongs to a particular type, but not for the type of an object.

from here

Hosch250

I guess I'm going to be spending today writing tests.

I only have one assignment, and I need to talk to one of my coworkers to get the business requirements because we lost them (big bus factor :/)

So, I'll write unit tests for the previous stages in this feature.

Duga

2:09 PM

[rubberduck-vba/Rubberduck] Vogel612 commented on issue #3038: 'Find All References' returns a factor of actual references

> What's the status on this? @rubberduck-vba/dev

[rubberduck-vba/Rubberduck] Vogel612 commented on issue #2919: No parsing, Pending/Refresh button doesn't trigger anything

> Hey @ReuK212 Can you try to check with the latest green release whether this still occurs? Thanks :)

Vogel612

there's quite a few [critical] issues out there ...

Duga

[rubberduck-vba/Rubberduck] Vogel612 removed label critical from issue #2326: Extract Method is broken

[rubberduck-vba/Rubberduck] Vogel612 commented on issue #2326: Extract Method is broken

> Since the refactoring has been disabled for now, this is not quite as critical anymore. Would still be great to get a fix ...

[rubberduck-vba/Rubberduck] Vogel612 commented on issue #3145: Parse Error & Crash on close (HRESULT: 0x800A01A8) in next branch v2.1.1981

> Can this still be reproduced?

[rubberduck-vba/Rubberduck] Vogel612 commented on issue #3058: Parsing issue: Library not registered

> @rubberduck-vba/dev is this still open?

M.Doerner

@Mat'sMug I think I messed up the registration there. The parse tree inspections do not get registered in the second call, because there is already a registration with the same name. I am just wondering why it does not throw an exception.

Instead of registering all inspections with all interfaces, one could register the parse tree inspections also with IInspection in the same statement.

Duga

[rubberduck-vba/Rubberduck] Vogel612 commented on issue #3347: Holy RAM, batman!

> #3405 could be related? We should reevaluate this after a fix for that is merged

[rubberduck-vba/Rubberduck] retailcoder commented on issue #3488: User Rubberduck only for versioning ?

> Thank you for your support.

FWIW you can disable inspections through the settings dialog, at the very bottom of the "inspection settings" tab there's a checkbox to "run inspections on successful parse" - un-checking that box will only run inspections when you click the "refresh" button on the *Inspection Results* toolwindow.

Alternatively you can selectively disable any/all inspection(s) by setting their severity level to "do not show".

That said, if inspections "take forever" to load

Mat's Mug

@M.Doerner ok I'll try that then

M.Doerner

2:24 PM

Add .WithService.Select(new[] {typeof(IInspection)})

It is a bit annoying, but in CW you can register a concrete type under the same name only once; the default name is the full type name.

Mat's Mug

IIRC there's a params overload, no need for the new[] {} ;-)

M.Doerner

No, there is no such overload. There is only an overload for a ServiceSelector.

Duga

[rubberduck-vba/Rubberduck] R0xtar commented on issue #3488: User Rubberduck only for versioning ?

> @Vogel612 Ouch, what a punch...

To answer to your points :

1. I saw this point but I can live with that, and why not contribute to improve this feature.
2. Ok for product's vision.
3. I don't want to ignore other Rubberduck's features, it would be amazing if I achieve to enable Ruberduck on our solution, but I tried hard since one week (without opening issue for things I think that could probably come forme our code base), so no disrespect here.
4. As I said, I'm very new to VBA deve

[rubberduck-vba/Rubberduck] R0xtar commented on issue #3488: User Rubberduck only for versioning ?

> @Vogel612 Ouch, what a punch...

To answer to your points :

1. I saw this point but I can live with that, and why not contribute to improve this feature.
2. Ok for product's vision.
3. I don't want to ignore other Rubberduck's features, it would be amazing if I achieve to enable Ruberduck on our solution, but I tried hard since one week (without opening issue for things I think that could probably come forme our code base), so no disrespect here.
4. As I said, I'm very new to VBA deve

Mat's Mug

@Duga you punched first..

Duga

[rubberduck-vba/Rubberduck] Hosch250 commented on issue #3488: User Rubberduck only for versioning ?

> 1. We are contributing to this feature. It started out back in 1.4.3, was greatly improved in 2.0.0, and was just recently made even more stable. There are still known bugs, though, and we are a small team and don't have time to contribute as much as we like.
4. If you are experienced with C#, feel free to help contribute yourself :). More contributors are always welcome.

As for the RAM problem, that is another known issue that we are working on; it is related to the parsing/resolving stag

[rubberduck-vba/Rubberduck] retailcoder commented on issue #3488: User Rubberduck only for versioning ?

> @R0xtar no worries (I *was* a bit irked by the idea of butchering 3 years' worth of work though ;-)

RAM consumption *is* an issue (see #3347), but it's the result of a deliberate and necessary memory-vs-performance trade-off in favor of performance, not of a memory leak - if there's a memory leak, it's most likely closer to COM interop and RCW's (e.g. commandbars, docked toolwindows) than any of the managed code, and definitely not perceptible through RAM monitoring (although possibly obser

Hosch250

2:42 PM

I'm becoming a bigger fan of the DB, if we can keep it completely invisible to the user.

Could we maybe even store data in it across sessions?

Mat's Mug

@Hosch250 yes

even across projects

Hosch250

Sweet :)

Mat's Mug

it's not like the VBA standard library changes every time we COM-reflect it

Hosch250

Projects? We already handle multiple projects in a session.

M.Doerner

We currently just COM reflect the references libraries every time because deserializing them takes even longer.

Mat's Mug

2:49 PM

yeah

and loading them from a DB would likely be even longer than that

Duga

[rubberduck-vba/Rubberduck] R0xtar commented on issue #3488: User Rubberduck only for versioning ?

> @Hosch250 I completely understand the resources/time problem for un free OSS project like Rubberduck is. That's why I totally respect amazing work that's done here.

With my issue, I see RAM consumption growing until usage hits 100%, but the Access process is still working (5-10% of CPU power) and Rubberduck writes parsing errors into the log file.

I'll take some time to try to help this project, my big problem here is lack of VBA knowledge, even if Rubberduck is written in C# I don't now

M.Doerner

I do not really know whether that is true.

Anyway, COM reflecting them does not take that long.

Duga

[rubberduck-vba/Rubberduck] retailcoder commented on issue #3488: User Rubberduck only for versioning ?

> @R0xtar haha @Hosch250 just so happens to hate VBA with a passion lol no worries about VBA knowledge, it's not a prerequesite at all :+1:

[rubberduck-vba/Rubberduck] Hosch250 commented on issue #3488: User Rubberduck only for versioning ?

> Don't worry, I have yet to write a useful program in VBA. My limit is hit with stuff like:

```
Sub Foo()
Dim fuzz As Integer
fuzz = 0
fuzz = 3
End Sub
``

[rubberduck-vba/Rubberduck] Hosch250 commented on issue #3488: User Rubberduck only for versioning ?

> Don't worry, I have yet to write a useful program in VBA. My limit is hit with stuff like:

```
Sub Foo()
Dim fuzz As Integer
fuzz = 0
fuzz = 3
End Sub
```

[rubberduck-vba/Rubberduck] Hosch250 commented on issue #3488: User Rubberduck only for versioning ?

> Don't worry, I have yet to write a useful program in VBA. My limit is hit with stuff like:

```
Sub Foo()
Dim fuzz As Integer
fuzz = 0
fuzz = 3
End Sub
```

As for the parsing errors, that is a whole new issue. Something in our grammar is broken.

[rubberduck-vba/Rubberduck] Hosch250 commented on issue #3488: User Rubberduck only for versioning ?

> Don't worry, I have yet to write a useful program in VBA. My limit is hit with stuff like:

```
Sub Foo()
Dim fuzz As Integer
fuzz = 0
fuzz = 3
End Sub
```

As for the parsing errors, that is a whole new issue. Something in our grammar is broken. Can you share the details with us? This is something we'll mark as a top-priority bug.

M.Doerner

3:08 PM

@Duga @Mat'sMug Growing memory consumption is new. Regarding the know quite stable 300MB or so, most of it is unmanged memory, most likely WPF caches; there is only about 120MB of managed memory used when running dotMemory.

Duga

[rubberduck-vba/Rubberduck] retailcoder commented on issue #3488: User Rubberduck only for versioning ?

> Agreed, the parsing errors are very very problematic, and a very likely cause for slow-downs if many modules are throwing exceptions. We'd need to see the logs =)

Mat's Mug

hmm

Duga

[rubberduck-vba/Rubberduck] MDoerner commented on issue #3488: User Rubberduck only for versioning ?

> Just two comments regarding the logs: to see parser errors, the log needs to be at least at level Error. Moreover, if your code is confidential, you might only want to provide the actual error entry as some log entries can reveal part of the code, especially at Trace level.

[rubberduck-vba/Rubberduck] R0xtar commented on issue #3488: User Rubberduck only for versioning ?

[rubberduck-vba/Rubberduck] Vogel612 commented on issue #3488: User Rubberduck only for versioning ?

> Re the first error: See #3058

Re the second: These warnings usually just mean that the parser has had a small problem when running on a faster "prediction mode". If the code does compile, Rubberduck usually can circumvent that by retrying the parsing in the slower mode. As long as you do not see actual Parser errors, these messages should only be a slowdown issue, not a breakage issue..

[rubberduck-vba/Rubberduck] retailcoder commented on issue #3058: Parsing issue: Library not registered

> @Vogel612 yup.

Vogel612

@Duga soo @IvenBach want to be assigned there?

Mat's Mug

3:23 PM

should be a simple fix, really

worth a hotfix release

Duga

[rubberduck-vba/Rubberduck] retailcoder commented on issue #3488: User Rubberduck only for versioning ?

> Gracefully failing to load a COM library is a known critical issue with a relatively simple fix that's... worth a hotfix release over the weekend.

[rubberduck-vba/Rubberduck] Vogel612 edited issue #3488: Use Rubberduck only for versioning ?

[rubberduck-vba/Rubberduck] R0xtar commented on issue #3488: Use Rubberduck only for versioning ?

> @Vogel612 The code compiles, I left my PC on all night long with Access on "parsing", and the results is that my log file grows to hundreds megs, Rubberduck eats all my RAM and Access is unusable (to slow).

That's why I thought that maybe our code base is too big to be handled by Rubberduck and wanted to just enable source control.

I'll try with the COM library fix and give you news asap.

@Vogel612 thank's for misspelling correction in the title

Hosch250

Oh my gosh.

Mat's Mug

@Duga that is new. wtf...

this

This is new? I thought that was pre-existing

In fact, yesterday I got OOM errors w/ Access eating up 1 GB memory

Vogel612

Sounds like an infinite loop of retries, if you ask me...

@this 32-bit?

this

3:35 PM

yes

Mat's Mug

@Vogel612 that

this

and I think I mentioned that I had a uncompilable code at one point

so it was locked in that forever parser error trap

which was already reported, too

Mat's Mug

in this case it seems to remain stuck in "Parsing" state though

this

Yeah but I did have that infinitely spinning ducks thing....

M.Doerner

That is strange. After the unexpected exception, it should go into state ParserError.

this

3:36 PM

(in my case, I think it had a error then saw the code changed, tried to parse but never finishing)

Mat's Mug

that's just a stupid IsBusy state never getting toggled back to false

this

makes sense. The CE stayed responsive

and as I mentioned yesterday, adding a module via CE knocked it back to the sense

then OOM came

Duga

[rubberduck-vba/Rubberduck] retailcoder commented on issue #3488: Use Rubberduck only for versioning ?

> hmm that's new... and very worrying... sounds like it's stuck in some infinite "retry" loop that somehow manages to skip the "clear cached state" part of the process... rest assured that the intent was definitely not that!

M.Doerner

I remember that there was some problem with the error dialog holding on to stuff and then trying to look at the component, which causes an infinite error state if the component is not there anymore.

That is one of the things I still have on my todo list.

Vogel612

more hotfixable stuff?

I guess it's good that we have a close release date :)

M.Doerner

3:42 PM

Well, part of it would be changing the what the module state event passes along. (It should pass the QMN, not the component.)

I will have a look after my exam.

puzzlepiece87

@Mat'sMug Do you mind if I BS check some SQL advice I heard with you?

IvenBach

@Vogel612 I will end up needing it to be fixed. In a fairly short time I'll end up fighting with it daily.

Not sure how hard it is to fix.

Vogel612

Well the try-catch there should be pretty obvious. You'd want to catch that exception and log a warning.

Additionally you can debug-log the exception information

Duga

[rubberduck-vba/Rubberduck] Imh0t3b commented on issue #3487: Duration of tool tips shown is too short if text contains more words

> Thank you Clements, the wiki starts with the Rubberduck.dll, but this is just for debugging new code. I'll keep your advices in mind and separate the issues. Translation standards, will be an issue too or did I miss a discussion on that (e.g. translate member to "Element" or not)

IvenBach

I'll definitely take a look at it.

Duga

3:55 PM

[rubberduck-vba/Rubberduck] Vogel612 commented on issue #3487: Duration of tool tips shown is too short if text contains more words

> Thank you Clemens, the wiki starts with the Rubberduck.dll, but this is just for debugging new code. I'll keep your advices in mind and separate the issues. Translation standards, will be an issue too or did I miss a discussion on that (e.g. translate member to "Element" or not)

[rubberduck-vba/Rubberduck] Vogel612 commented on issue #3487: Duration of tool tips shown is too short if text contains more words

> Hä? Ich verstehe den zweiten Satz nicht so ganz. Worauf willst du hinaus?

Vogel612

better switch to German there...

Duga

[rubberduck-vba/Rubberduck] rubberduck203 commented on issue #3488: Use Rubberduck only for versioning ?

> Just to jump in here for a moment, if all you need is source control, I would look into one of the other solutions for Access. There are a number of projects (of varying quality) for getting VBA into source control. I do think our project offers other benefits, but may not be best for meeting your immediate need.

Mat's Mug

we're such a cosmopolitan repository :)

Duga

[rubberduck-vba/Rubberduck] Vogel612 commented on issue #3487: Duration of tool tips shown is too short if text contains more words

> Hä? Ich verstehe den dritten Satz nicht so ganz. Worauf willst du hinaus?

[rubberduck-vba/Rubberduck] Imh0t3b edited issue #3487: Duration of tool tips shown is too short if text contains more words

Vogel612

third, not second :/

M.Doerner

3:57 PM

The question is where to catch it, in GetComReferencesToLoad or actually in Reference.FullName and return String.Empty?

Mat's Mug

I was thinking that would be cleaner at the wrapper level

M.Doerner

That is also my preference.

However, I do not know whether the error pops up afterwards again.

Hm, I think we are already loading the declarations inside a try catch.

Duga

[rubberduck-vba/Rubberduck] Imh0t3b opened issue #3489: Version String should be copy-able from about window

> I had to write my current version by hand instead of just copying it from the about window.

M.Doerner

It is just that the name is requested before trying to load the reference.

Duga

[rubberduck-vba/Rubberduck] Imh0t3b edited issue #3489: Version string should be copy-able from about window

[rubberduck-vba/Rubberduck] retailcoder added label enhancement to issue #3489: Version string should be copy-able from about window

[rubberduck-vba/Rubberduck] retailcoder added label hacktoberfest to issue #3489: Version string should be copy-able from about window

[rubberduck-vba/Rubberduck] retailcoder added label up-for-grabs to issue #3489: Version string should be copy-able from about window

[rubberduck-vba/Rubberduck] retailcoder added label user-interface to issue #3489: Version string should be copy-able from about window

[rubberduck-vba/Rubberduck] retailcoder added label difficulty-01-duckling to issue #3489: Version string should be copy-able from about window

[rubberduck-vba/Rubberduck] retailcoder added label good first issue to issue #3489: Version string should be copy-able from about window

[rubberduck-vba/Rubberduck] Imh0t3b edited issue #3489: Version string should be copy-able from about window

[rubberduck-vba/Rubberduck] retailcoder commented on issue #3489: Version string should be copy-able from about window

> Let's make Ctrl+C on the about box put the version string into the clipboard, and make the version label display a little dropdown menu on click, with "Copy to clipboard" as the sole item.

Hosch250

4:06 PM

@Duga Just an icon, not a menu.

Duga

[rubberduck-vba/Rubberduck] bclothier commented on issue #3489: Version string should be copy-able from about window

> May I suggest that the copying take in the environment, too? (e.g. Windows, which VBA host application & its version, 32/64 bit)? Those are commonly needed in diagnosis, no?

Hosch250

NAFAIK.

Rarely, sure.

Well, host application, yes.

Windows version, host app version, NAFAIK.

32/64 bit, pretty rare.

Pinlop

is there anyway one of you guys could take a look at this for me? stackoverflow.com/questions/46851310/…

Duga

[rubberduck-vba/Rubberduck] Imh0t3b commented on issue #3487: Duration of tool tips shown is too short if text contains more words

Pinlop

I'm still tinkering with an idea Mat'sMug gave me a while ago and still can't figure it out

puzzlepiece87

4:11 PM

@Pinlop I never work with tables, sorry. I don't have enough experience to help.

M.Doerner

@Duga All this information is available at the top of the log.

Pinlop

Would you know how to convert Array.Values into a Range?

without having to actually assign it to a range on any worksheet?

Duga

[rubberduck-vba/Rubberduck] MDoerner commented on issue #3489: Version string should be copy-able from about window

> @bclothier All this information is also available at the top of the log file.

Pinlop

That's my main problem. I don't need to actually work with any tables, I just need to be able to have a range of my values that i can copy

but I can't have that range be part of any worksheet

IvenBach

@Pinlop I'm currently reading through your post. So far it seems a small subset into a new array is the best option.

From what I've understood.

based on Zerk's comment the range(x.cells(1,1),x.cells(ubound(testArray,1),ubound(testAr‌ray,2))) = testArray does seem to fit what I was thinking of. Just be sure to fully qualify the Range with which Worksheet you want it to be deposited to. Otherwise it's the activesheet.

Duga

4:19 PM

[rubberduck-vba/Rubberduck] bclothier commented on issue #3489: Version string should be copy-able from about window

> @MDoerner I suspected that was the case; I was thinking about when users doesn't have the log available/handy.

Pinlop

@IvenBach Yeah, Zerk had been helping me think through this and he suggested the same thing. My problem is that the reason I'm looking to do things this way, is because I already have a version of this code that will copy the columns I need onto Sheet2, and I want to eliminate the need for having to copy anything onto sheet2

What I wish I could do is just grab all these values, and somehow turn them into what VBA recognizes as a Range (not attached to any worksheet) and then copy it

somehow union the values I need into one floating Range

Probably not possible...

Duga

[rubberduck-vba/Rubberduck] retailcoder commented on issue #3489: Version string should be copy-able from about window

> Can't hurt to have it either, but the redundancy of it makes it a not-quite-high-priority issue. Up for grabs!

IvenBach

I don't know if you can do directly from array elements into a range variable. Using a smaller temp array will let you paste into an equally sized range.

this

Have fun, everybody. Gonna be off the grid for the weekend!

M.Doerner

Have a nice weekend.

Duga

4:27 PM

[rubberduck-vba/Rubberduck] Vogel612 commented on issue #3487: Duration of tool tips shown is too short if text contains more words

> Also es gibt sowohl Übersetzungen als "Member" als auch als "Mitglied", aber anscheinend noch keine als "Element" ...

[rubberduck-vba/Rubberduck] Vogel612 commented on issue #3487: Duration of tool tips shown is too short if text contains more words

> Also es gibt sowohl Übersetzungen als "Member" als auch als "Mitglied", aber anscheinend noch keine als "Element" ... Sollte man sich ggf. mal drüber unterhalten :sweat_smile:

M.Doerner

As far as I understand it, a range variable is basically a reference to a part of a worksheet with some methods attached.

I think there cannot be a range without an underlying actual range in a worksheet.

Mat's Mug

Range.Parent is always an Excel.Worksheet object reference; Range.Application is always an Excel.Application object reference. There's no such thing as a "standalone" or "detatched" Range instance.

M.Doerner

And there are also no detached worksheets or workbooks.

IvenBach

@this Enjoy. Thanks for the help yesterday too. I really appreciate it.

Duga

[rubberduck-vba/Rubberduck] Imh0t3b commented on issue #3487: Duration of tool tips shown is too short if text contains more words

> Hab ich von Leo gefällt mir besser als Mitglied. Wir gehen aber jetzt ganz schön OT, wäre ein eigenes issue oder?

Mat's Mug

4:33 PM

@this enjoy the break!

Duga

[rubberduck-vba/Rubberduck] IvenBach commented on issue #3487: Duration of tool tips shown is too short if text contains more words

> I too had wanted to make the tooltips duration longer. A checkbox to enable a inputbox for a time duration? Or right click to have it display the tooltip without a timer?

[rubberduck-vba/Rubberduck] Hosch250 commented on issue #3487: Duration of tool tips shown is too short if text contains more words

> It should display as long as the user is hovering over it.

[rubberduck-vba/Rubberduck] IvenBach commented on issue #3487: Duration of tool tips shown is too short if text contains more words

> It displays for 5 seconds, even if the cursor is still hovering. IIRC Mug mentioned this being the default timer.

[rubberduck-vba/Rubberduck] retailcoder commented on issue #3487: Duration of tool tips shown is too short if text contains more words

> It's a 2-seconds, 1-liner fix in the XAML markup.

[rubberduck-vba/Rubberduck] R0xtar commented on issue #3488: Use Rubberduck only for versioning ?

> I didn't found anything else that's open source and for me it sounds like a requirement for a source control tool (I'm not scarred about my code being stolen, it's about principles).

I'll think about it this this weekend and take a look to Rubberduck's source code and see if I can do anything that could also help the community.

3

Transcript for