« first day (2136 days earlier)      last day (1044 days later) » 

12:00 AM
RELOAD!
[Minesweeper] Games Played: 187, Bombs Used: 125, Moves Performed: 24316, New Users: 38
 
 
6 hours later…
5:41 AM
@M.Doerner I'm tempted to say that they should accept 'my' answer if it helped them so much. codereview.stackexchange.com/questions/240249/…
 
 
13 hours later…
6:51 PM
Why does SortRange.Sort Key1:=.Cells(1, SortColumn), order1:=SortDirection cause a FunctionReturnValueDiscardedInspection?
 
7:43 PM
Good question
 
Starting to use inspections to clean up my sins and am running into several that seem odd. Like this: ``` With SheetToUse
Set SortRange = .Range(.Cells(1, 1), .Cells(.UsedRange.Rows.Count, .UsedRange.Columns.Count))``` throwing IndexedDefaultMemberAccessInspection...
is there a way to put code into chat so it is more readable via Markup?
I've tried several ways none of which does the trick
 
8:07 PM
You can use single backticks for inline code formatting.
It does not work for multi-line input, though.
There, the fixed font toggle button is your friend.
 
that was what I was trying to do.. so I'd have to do each line independently..
<showing my ignorance> fixed font toggle?
 
Btw, the indexed default member access is in Cells(1,1), which basically expands to Cells.Item(1,1).
 
ok... so that will fix those?
 
In the desktop version, when you have multi-line text, it is on the right of the input field.
The problem here is that the quickfix actually expands it to Cells.[_Default](1,1), because of how the default member of Range is set up.
Cells only exists because of a design sin around the Range class.
It saves whether it consists of single cell, columns or rows internally, but does not expose it to the user.
Cells forces the range to consist of single cells.
Btw, the IndexedDefaulemberAccessInspection has level hint for a reason.
 
Got time for another Inspection question?
 
8:17 PM
In VBA, it is rather idiomatic to access collections without explicitly writing out the Item member.
Sure
Shoot.
 
MemberNotInInterfaceInspection : Application.WorksheetFunction, Application.PathSeparator, etc.
Application.ScreenUpdating
 
I am not sure these are actually on the interface for Application. However, I would have to have a look at the Excel library.
 
They pop up in Intellisense, so ...
but then I don't understand all I probably need to
 
8:38 PM
If I have a worksheet having its Codename myWS and then have a Type variable WS As Worksheet then Set this.WS = myWS throws SetAssignmentWithIncompatibleObjectTypeInspection
 
 
1 hour later…
9:50 PM
RD currently does not know that myWS is a Worksheet. The VBE does not expose that directly and we still have not wired up the typeLib API that can get that information using black voodoo.
 

« first day (2136 days earlier)      last day (1044 days later) »