> Losing the attribute should be fixed, but @ThunderFrame's idea should still be implemented:
```vb '@HotKey("T") Public Sub DoSomething() Attribute DoSomething.VB_ProcData.VB_Invoke_Func = "T\n14" End Sub ```
The hotkey string/character is case-sensitive, and the <kbd>Ctrl</kbd> modifier is implicit. The attribute value simply needs to take (+validate) that character, append `"\n14"` (which presumably stands for the <kbd>Ctrl</kbd> modifier key).
> Losing the attribute should be already fixed now, but @ThunderFrame's idea should still end up being implemented:
```vb '@HotKey("T") Public Sub DoSomething() Attribute DoSomething.VB_ProcData.VB_Invoke_Func = "T\n14" End Sub ```
The hotkey string/character is case-sensitive, and the <kbd>Ctrl</kbd> modifier is implicit. The attribute value simply needs to take (+validate) that character, append `"\n14"` (which presumably stands for the <kbd>Ctrl</kbd> modifier key).
> **Justification** Unless you're recording your macro, assigning a hotkey is annoying. So annoying, that most give up the obscure declarative (attribute) syntax and resort to a much less maintenance-friendly dynamic solution involving `Application.OnKey`.
Linking #3348.
Now that Rubberduck can add & modify member attributes and keep them in sync with annotation comments, implementing this should not only be fun and fairly trivial, it's also a very useful and rewarding feature to write.
> Version 2.4.1.37597 OS: Microsoft Windows NT 10.0.17763.0, x64 Host Product: Microsoft Office x86 Host Version: 16.0.11601.20178 Host Executable: EXCEL.EXE
**Description** Collapse and expand buttons for grouping expand all and collapse all.
**To Reproduce** Steps to reproduce the behavior: 1. Have inspection results. 2. Click on a grouping header to expand/collapse that header. 3. See all headers expanded/collapsed.
**Expected behavior** Each header will expand/collapse ind
> # [Codecov](https://codecov.io/gh/rubberduck-vba/Rubberduck/pull/4961?src=pr&el=h1) Report > Merging [#4961](https://codecov.io/gh/rubberduck-vba/Rubberduck/pull/4961?src=pr&el=desc) into [next](https://codecov.io/gh/rubberduck-vba/Rubberduck/commit/6134c87f139b5578a667a3e929054b6e7ec73393?src=pr&el=desc) will **decrease** coverage by `0.01%`. > The diff coverage is `94.74%`.
> # [Codecov](https://codecov.io/gh/rubberduck-vba/Rubberduck/pull/4961?src=pr&el=h1) Report > Merging [#4961](https://codecov.io/gh/rubberduck-vba/Rubberduck/pull/4961?src=pr&el=desc) into [next](https://codecov.io/gh/rubberduck-vba/Rubberduck/commit/6134c87f139b5578a667a3e929054b6e7ec73393?src=pr&el=desc) will **decrease** coverage by `0.01%`. > The diff coverage is `94.74%`.
Declaratively adding hotkeys to an #Excel #VBA macro is a bit ...arcane. How about making a new Rubberduck annotation instead?
'@ExcelHotKey("A")
Public Sub DoSomething()
'...
End Sub
#CSharp #OSS #UpForGrabs #Contribute #YouCanDoThis
https://github.com/rubberduck-vba/Rubberduck/issues/4959
Czech translations are now all up-to-date in the latest pre-release build: https://github.com/rubberduck-vba/Rubberduck/releases/tag/Prerelease-v2.4.1.4704
Thanks again @SonGokussj4CZ!
#OSS #localization #kudos
Had a nice read about DI here in VBA:
https://rubberduckvba.wordpress.com/2016/07/05/oop-vba-pt-2-factories-and-cheap-hotels/
So now the next step would be use an IoC container in VBA. But I am wondering if that's even possible! I'm new to VBA and I cant figure out a few things:
If done in VB...
> I submit that if you've reached the point where an IoC container makes sense for your VBA project and you understand everything about DI and SOLID and write your code accordingly... then [not to take anything away from VBA but] my assessment is that you're completely ready to move on from VBA and work with more OOP-capable languages, such as VB.NET or C# - and use everything you've learned about OOP in VBA [...]
Oh, the irony. The "VBA is a perfectly fine OOP language" guy just said "if you know OOP, move on from VBA"
I think that's been long ago established the day you returned to the pond on day #2
Morts usually either a) doesn't even know there's a pond or b) stumbled once in their aimless wandering and kept on wandering, discarding any help or answers given
I can understand not hearing back for a resume, but after an interview I'd expect the company to send at least some indication that they're not interested...
IDK, taking a $10K-$20K drop to avoid being forced to work on-prem downtown (and thus keep my sanity), while being the sole source of revenue for the family... stresses the crap out of me :)
git log does that for you. You basically only need reflog when you broke something
reflog is basically the undo stack for git
seeing your PR I assume you want to have the commits "Replace literal string in favor of nameof()", as well as "Add filtering for TestExplorer" and "Sort filter list"
> # [Codecov](https://codecov.io/gh/rubberduck-vba/Rubberduck/pull/4956?src=pr&el=h1) Report > Merging [#4956](https://codecov.io/gh/rubberduck-vba/Rubberduck/pull/4956?src=pr&el=desc) into [next](https://codecov.io/gh/rubberduck-vba/Rubberduck/commit/6134c87f139b5578a667a3e929054b6e7ec73393?src=pr&el=desc) will **decrease** coverage by `0.03%`. > The diff coverage is `31.03%`.
@IvenBach I think the ICollectionView Tests should be modified in the constructor not only to have SortDescriptions but also FilterProperties. That should change the way you wire up the filtering a bit...
I'm not 100% sure how it works, but setting the Tests.Filter every time seems wrong to me.
> # [Codecov](https://codecov.io/gh/rubberduck-vba/Rubberduck/pull/4956?src=pr&el=h1) Report > Merging [#4956](https://codecov.io/gh/rubberduck-vba/Rubberduck/pull/4956?src=pr&el=desc) into [next](https://codecov.io/gh/rubberduck-vba/Rubberduck/commit/6134c87f139b5578a667a3e929054b6e7ec73393?src=pr&el=desc) will **decrease** coverage by `0.03%`. > The diff coverage is `31.03%`.
> # [Codecov](https://codecov.io/gh/rubberduck-vba/Rubberduck/pull/4956?src=pr&el=h1) Report > Merging [#4956](https://codecov.io/gh/rubberduck-vba/Rubberduck/pull/4956?src=pr&el=desc) into [next](https://codecov.io/gh/rubberduck-vba/Rubberduck/commit/6134c87f139b5578a667a3e929054b6e7ec73393?src=pr&el=desc) will **decrease** coverage by `0.03%`. > The diff coverage is `31.03%`.
<DataGridTextColumn Header="Description" Width="*" DisplayIndex="{Binding DescriptionIndex, FallbackValue=3}" /> is giving me the expected result in the designer but I don't get any change when I reorder the column.
Hi guys. I need help. Any idea would be nice. I transformed my project logic. (excel)
I've got Module 'mControls' where I have defined 'Public activeControls As New Scripting.Dictionary'.
On my form code-behind, I've got procedure 'InitControls frm:=Me' which iterates over all controls and initialize each of them to their respective class (clsUserListBox, clsUserTextBox, ...) And then sets them into dictionary.
Dim userLst As clsUserListBox
Set userLst = New clsUserListBox
userLst.InitializeWithValues lstCtrl, frm
Debug.Print "Adding [" & userListBoxName & "]"
' userListBoxName is combination of 'formsname_ctrlname'
Set activeControls(userListBoxName) = userLst
Now the form appears, I do stuff with it and when I'm done I press Cancel/Save and I kill the form (no hide yet) and it disappears.
Now the problem is - I have still in memory, in that public 'activeControls' dictionary them user classes.
What's the best way (where to write the code) to resolve this? Should I iterate over all forms controls on Save/Exit/X and delete my userControls from that dictionary if the Key equals 'formname_ctrlname'?
My head is really confused about the right procedure here...
For now, I have:
''''''''''''''''''''''''''''''''''''
' Form closed by X or BTN - btnClose
'---------------------------------------------------------------------------------------
Private Sub UserForm_QueryClose(Cancel As Integer, CloseMode As Integer)
Dim ctrl As MSForms.Control
For Each ctrl In Me.Controls
Dim ctrlFullname As String
ctrlFullname = Me.Name & "_" & ctrl.Name
If collUserListBox2.Exists(ctrlFullname) = True Then
collUserListBox2.Remove ctrlFullname
End If
But thinking if there is a better way so I don't have to do this on each form_QueryClose
Had a nice read about DI here in VBA:
https://rubberduckvba.wordpress.com/2016/07/05/oop-vba-pt-2-factories-and-cheap-hotels/
So now the next step would be use an IoC container in VBA. But I am wondering if that's even possible! I'm new to VBA and I cant figure out a few things:
If done in VB...
VBA Rubberducking
VBA Rubberducking