REFRESH!

[Minesweeper] 80 Games Played. 55 Bombs Used. 10211 Moves Performed. 10 New Users

Function MakeRange( _
    ByVal Sld As Slide, _
    ByVal WantedShapes As String _
) As ShapeRange
    Set MakeRange = Sld.Shapes.Range(WantedShapes)
End Function

This looks ugly to me bc the indentation of the parameters aligns with the indentation of the function body. Any suggestions as to how to improve?

Function MakeRange( _
        ByVal Sld As Slide, _
        ByVal WantedShapes As String _
) As ShapeRange
    Set MakeRange = Sld.Shapes.Range(WantedShapes)
End Function

This looks even uglier.

Function MakeRange(ByVal Sld As Slide, ByVal WantedShapes As String) As ShapeRange
    Set MakeRange = Sld.Shapes.Range(WantedShapes)
End Function

put the parms on one line

I don't want to do that though, too long

And will get longer if I add more params

Been writing too much Python lately and it's bleeding over into VBA lol

Function MakeRange( _
              ByVal Sld As Slide, _
              ByVal WantedShapes As String _
    ) As ShapeRange
        Set MakeRange = Sld.Shapes.Range(WantedShapes)
    End Function

hahahahahahaha

ah maybe I laughed too soon... seems like you're suggesting the second option I proposed?

well, that ain't working. Line up ByVal directly below MakeRange or line it up inside the ( paren

more or less, but make the spacing more vertical.

I usually put my parms on one line. If I have too many, I indent until they line up withing the ( on the 2nd line. Heaven help me if they wrap to a 3rd line!

ah yeah I can visualize that

are there any options in RD's indenter around this? Maybe pick one and use it just to make your life easier and so running the indenter doesn't break anything custom you've come up with.

good idea

not sure

I have not installed RD on my work machine

```

```

@BigBen FWIW I've landed on lining up the parameters the same as the function body much like your initial example - except that I would include the function's ') As ShapeRange' statement on the same line as the last parameter. Then, I add a blank line between the last line of the function declaration and the first line of the function body for a clear distinction between the end of the declaration and the start of the code.

Yah I thought about something like this, including the blank line!

The blank line would definitely help

Sure! I've recently been trying to keep my line lengths around 80-ish lately - creates all sorts of new formatting 'decisions'. :)

i guess i could look up some powershell options, as they may exist... hm

dealing with removing items from a network drive, and rather than taking 1 day per 2 GB delete, i should be able to circumvent that with commands

and heck yeah; didn't realize IT gave me back my powershell access... we deleting all the stuffs (1 by 1, though... my VPN times out after 8 hours of use, and i dont' know how long each folder will take; timing the first, now)

1.5 hours to delete a 2 Gb file.

@Cyril When I was a child I remember writing a QBasic program called "KILLDIR" for this explicit reason. I was so happy that 4.5 could compile to native binary. I was making tools instead of batch files.

I have this memory because the answer is "no". DOS makes it hard to delete directories that are full of shit

[rubberduck-vba/Rubberduck] ofir-bar starred us

[rubberduck-vba/Rubberduck] 1624 stars vs. [decalage2/oletools] 2158 stars