Is there a more appropropriate way to list a parameters datatype for functions? Public Function GetColor(ByVal Cell As Range, Optional boolGetFontColor As Boolean = False) As Long If boolGetFontColor Then GetColor = Cell.Font.Color Else GetColor = Cell.Interior.Color End If End Function
My understanding is Cells with an s is a container or ?interface which VBA allows me to select which index to it. Cell would be a method which usi within a WITH block allows accessing a property of that type.
you make a commit with a commit message that references the issue# with the word "closes", e.g. "closes #1234", and when that commit gets merged (via a PR) then the issue gets closed
but yeah, the "making a commit" part is best done in VS :)
you can get VS2013 or VS2015 Community Edition for free
here's a WTF - Add an ActiveX button to a sheet. It will get a default name like "CommandButton1", and there's an invisible WithEvents CommandButton1 As CommandButton declaration in the code-behind and you can wire up events for it....
Now, select the button and rename it to any name that is in the list of Worksheet member names, such as Name. The code-behind still uses the previous name for the WithEvents variable, but Sheet1.OLEObjects("Name") returns the object?!?!
@Mat'sMug @Comintern I finished helping my coworker with her massive .csv. Thank you both so much for your help! Now I'm on to posting the first of my programs to CR as we talked about. Keeping in mind our earlier conversation about code blocks and sections and your advice that I probably should have broken the module into multiple procedures or functions, how should I go about posting my program to CR? Should I attempt to break it up first, or just divide and commentate ...
@Comintern Public Sub Resize_Selection(ByVal isRow As Boolean, ByVal isIncrease As Boolean)
Dim Crement As Long
If isIncrease Then
Crement = 1
Else
Crement = -1
End If
Dim rSource As Range
Set rSource = Selection
Dim R2 As Range
For Each R2 In rSource.Areas
Dim Size As Long
If isRow Then
Size = R2.Rows.count + Crement
Else
Size = R2.Columns.count + Crement
End If
If Size = 0 Then
MsgBox ("Part of your selection has only 1 Column and/or Row." & Chr$(10) & "You cannot further decrease …
There doesn't seem to be any way of inspecting the Sheet1.OLEObjects("Name") or Sheet1.Shapes("Name")` to discover what the underlying variable name is.
@IvenBach the inspection names are all on the website's /inspections/list page - the annotation will take anything you throw at it, but is meant to be parameterized with inspection names (minus the "Inspection" suffix)
Note that some of the inspections on the website aren't in 2.0.11, the website uses an old .12 build
huh, explicitly casting the OLEObject.Object gets access to the name property...
Dim oleobj As OLEObject
Set oleobj = Sheet1.OLEObjects("Name")
Debug.Print TypeName(oleobj.Object) 'Prints "CommandButton"
Debug.Print oleobj.Object.Name 'Runtime error 438 - Object doesn't support this property or method
Dim cb As CommandButton
Set cb = oleobj.Object
Debug.Print cb.Name 'Prints "NameFoo"
@IvenBach good question.. make it an issue and worst-case we'll close it as a dupe, or no-repro if it's already fixed and we can't find the issue for it
How is this even possible? If I change the reference collection on the Declarations to be a ConcurrentDictionary<IdentifierReference,byte>, the test TestPlusOperator starts failing whan I run all tests, but not when I debug it. That test only uses the precocessing visitor.
> Tied to #2753. Once you undo to get it back to normal without 'Auto Syntax Check' red you need to resolve the 'Parse Error'. On doing that Dim ParameterList As Range is deleted.
> It's possible to add an ActiveX control to a sheet, and name the hosting `Shape` as `Name` which shadows/conflicts with the `Name` property of a Worksheet class. That makes for a disconnect between the shape name and the name of the `WithEvents` object that sources events in the sheet's code-behind.
RD should have an inspection that looks for such naming conflicts.
The VBA to get the real control name requires explicitly casting the `OLEObject.Object` to the underlying type:
gah, an Access control name can shadow a form member name. OB shows the name as the WithEvents object, but VBA usage is the form member, and yet the events still fire.
> When the move is successful it appears like the indentation from where it was moved FROM is preserved and may not be the same as where it was moved TO.
VBA Rubberducking
VBA Rubberducking