[retailcoder/Rubberduck]MDoerner pushed commit 096c0851 to next: Moved wrongly positioned try catch into the dispatched delegate in AppCommandBarBase and added further try catch blocks around COM interaction.
[retailcoder/Rubberduck]MDoerner pushed commit 0faae3f9 to next: Introduced catch, log and swallow approach for all exceptions in delegates dispatched to the UI thread.
```vb Sub testNull() Dim a As Variant Dim b As Double
a = Null b = 0
If a = Null Then MsgBox (a & "null") 'doesn't print ElseIf a <> Null Then MsgBox (a & " not null") 'doesn't print Else MsgBox (b & " don't know") 'prints End If
@Mat'sMug Yes the exception is unexpected. Moreover, the other change in the commit would have been even worse since it would have disabled all our parsing error reporting.
@Kapol There are multiple solutions to our problem with the cyclic dependency regarding the settings. I will write a comment regarding this in the corresponding issue. Then we can see which way we want to go.
> I strongly object to ignoring the .frx files by default. This makes the repo lose all "design" information of the forms which can be **a lot of work** to redo.
Instead I think we should be intelligent about only replacing the .frx file in the repo when it *actually changed*. [VbaDeveloper](https://github.com/gkuenzli/vbaDeveloper) (a VBE addin to export source code during each Excel file save) has a great [feature idea](https://github.com/gkuenzli/vbaDeveloper/issues/2) regarding this. It s
> @Merlin2001 agreed - the .frx includes vital binary information including and not limited to embedded icons and whatnot: outright ignoring these files means data loss, and that can't work. Thanks for the ideas!
I have a little problem with the TestExplorer and testing if two dictionaries are equal
Dim Dict As Scripting.Dictionary Dim DictOrig As Scripting.Dictionary Dim Item1 As New Collection Dim Item2 As New Collection Dim Item3 As New Collection
Set Dict = StrToDict("table: CURVE; headers: [ID, NUM]; clickable: True") Set DictOrig = New Scripting.Dictionary
I'm currently designing a check list for my office using Excel that requires the user to save anywhere from 4-10 documents that need to be saved in the same folder as this check list. I thought it might be easier to consolidate everything into one Excel file by using User Forms. I noticed that it...
/// <summary>
/// Verifies that all of the items in 2 arrays are equal. The assertion fails if any items is different, if either the lower
/// bounds or upper bounds are different, or if the ranks (number of dimensions) differ. This can be used for arrays of arbitrary
/// dimensions and arbitrary bounds.
/// </summary>
/// <param name="Expected">The expected sequence.</param>
/// <param name="Actual">The actual sequence.</param>
/// <param name="Message">An optional message to display if the assertion fails.</param>
yup, with an s
note the documentation explicitly states it's for comparing 2 arrays
@SonGokussj4 that [Description] attribute actually populates the member description text if you're early-binding and viewing the library in the object browser
yeah. we'll have to do that. Otherwise, the documentation will never be updated.
the nice-to-have bow ribbon on the top would be a way to connect the changes on xmldocs to the wiki articles, so we can see which may have been obsolete and thus needs review.
because xmldocs are primarily good for what but not so good for why or the big picture.
> NOW HIRING: documentation writers, technical writers. Awesome team, PTO as needed, paid on delivery with many "thanks!" and tons of recognition, and possibly yearly with a mug and/or a t-shirt and other swag. APPLY NOW!
> First of all, I have not tried to figure out where the CW exception is coming from, so far.
Let me recapitulate where the circular dependency in PR #3534 is coming from. After that I will pose some design/functionality questions to determin whether the settings file actually solves the problem. Finally, I would like to point out some opions we have in case we want to take the route where the circular dependency cannot be avoided easily.
> First of all, I have not tried to figure out where the CW exception is coming from, so far.
Let me recapitulate where the circular dependency in PR #3534 is coming from. After that I will pose some design/functionality questions to determin whether the settings file actually solves the problem. Finally, I would like to point out some opions we have in case we want to take the route where the circular dependency cannot be avoided easily.
> First of all, I have not tried to figure out where the CW exception is coming from, so far.
Let me recapitulate where the circular dependency in PR #3534 is coming from. After that, I will pose some design/functionality questions to determine whether the settings file actually solves the problem. Finally, I would like to point out some options we have in case we want to take the route where the circular dependency cannot be avoided easily.
Lots of little stuff I knew started clicking into place once I finally saw what all the alphabet soup 1 and 2 letter variables were doing. Sounded like Snap, Crackle, Pop for a while in my brain.
The code below does the following:
Look through rows 10 and the lastrow of a sheet, and based off certain criteria, loops through each row
If the scenarios match, then the code will drop in 0s and 1s onto another sheet in a formulated range
In some scenarios, the code will fill down formulas.
...
Blargh.... Who'd have thought changing a single variable assuming it wouldn't break anything would take me 30 mins to figure out how to properly correct it. Wish I had unit tests for this. #GladItsATestingEnvironment
The axe wielding lunatic makes so much more sense now.
Hosch, but see, my problem with the TS (or even F# transcompiling) is that you are just building on the top of abstractions. When it goes wrong, you're hared.
when i look at a typical front-end web developer toolkit, I think that they use wayyy too much tools.
You sound a lot like the hex programmers when Assembly came along, and like the Assembly programmers when C came along, and the C programmers when C++ came along.
My company is, but we specialize in Access work. We do lot of Office automation, so VBA skills should be easy to translate between Office products. If you don't mind working with Access projects, apply away.
Sorry I couldn't be more helpful. That's what we usually do when our clients come to us with unmanageable excel spreadsheets -- we convert them into Access applications that generates Excel reports.