Gonna do some refactoring in my Excel app. I've got some huge data classes that need to be trimmed down into smaller sets of data, then have the routines that populate said data incorporated.
Is there a handy feature of RD that will assist with this, or is this a manual copy/pasta & figure out what you just broke?
create a class with x, y, z, foo, bar, baz, none of which much exist be populated, then DoIt sorts out what is to be done based on which elements are populated in the class instance passed in.
Boss called yesterday, apparently I have one more week of work, beyond that, my 97 years old company/employer might have to let go of its IT operations.
@this a legit TortoiseGit question for you: I just removed a bunch of functions from a class that I didn't mean to (at least not yet...) They came from a variety of locations throughout the class, so I don't want to just paste 'em all in at the end to restore functionality because that would be a positive diff. ATM, there's no reason for this class to be changing.
In TG's diff, there's a Use left block button. Will that simply update my currently exported code module with the original contents that git is holding, then I can reimport that one module to the project to be back where I was?
I think that if I click that button, my code moves to the right, from what git currently has stored to what is in my actual on-disk file that I'm working from, right?
not that it adds to your learning, but i remember having more problems with solo-projects in git than i did with group projects, just because the owners had mandates... i got sloppy with my commits when solo.
back to work related items... me thinks me needs another refactor. In my class I have ytdValueA and lastYearValueA. I think I need a new class that has valueAandYearFlag, then have a collection in the existing class that holds 2 instances, one for this year, one for last year.
Note: ValueA === foo. No numeric- or alphabetic-suffixed variable names have been employed in the building of this class
Hmm how interesting. my Word seized up after I made a simple document with only 2 words, and tried to save. After forcing it to close, I got the old dialogs "trying to recover blah". I have not seen that in a while.
@Cyril basically yeah and yeah. I think that would be the best bet, long run. I've been running this report for 3-4 years and we've never reported anything beyond YTD and LastYearsEndValue, but that doesn't mean it won't change at some point in the future...
I've got an '@TODO for the further refactoring. I'm not going to tackle that on the first pass, though
RD Question: I've just added a couple of '@Description("") annotations & inspected. I get the full suite of Fix all in {x} options. Since there are two possible fixes (update/create the attribute or delete the annotation), which one is gonna happen if I click a Fix all?
Most (all) other inspections have a Fix or Ignore option, so the Fix All is obvious
1) Copy just in case
2) Click "Fix all in module"
3) ???
4) Profit!!!!
It appears to execute the update/create the attribute quick fix. Logical but not obvious...
the two key points, 1) people can't remember how to get to particular file extension, so MS will give you the list of folders you recently used, and 2) it's more friendly to things like SharePoint since it resovles addresses as folders, rather than https
carp. '@Description annotations on elements of a Type embedded in a class don't flow through to the Get`Let` functions. Nor does the annotation on the Get propagate to the Let. Makes sense, but would be super handy...
i like to relate all of this to Intuit (TurboTax); your business model is driven by making things complicated, and having others support making it complicated so they can also make money. 2004 (i believe) it was signed/mandated that by 2010 the IRS must offer a free service to do your taxes. Intuit spends billions per year to both ensure the IRS makes that difficult to find on their webpage and stifles efforts to have tax reform that would negatively impact their bottom line.
the relative point being, MS is making things "harder" along with their competitors, and telling you it's "good for you" (e.g., having those "talks" to discuss with the users)
Prolly' gonna go the way of Skype now. Take a good product. Attempt to extract the core features. Build your own product. Release product with inferior features and performance to poor review. Kill original product. Call it "PROGRESS!!!!"
in 2016, MS bought LinkedIn; in 2018, office365 integrated your MS account to your LinkedIn account (by email, behind the scenes). Since 2019, "LinkedInLearning" has existing, where people post tutorials on LinkedIn, in a pay-to-view scenario, where the most used videos are about Excel and Word. The tie-in to LinkedIn allows MS to get more data about what is being used in their programs to put in more videos, and tailor the suggestions.
I did a Save As after disabling that middle feature in the 1st image. It still showed additional places for saving, even if sign-in may be required.
Maybe since I'm on a corp network and I technically don't have to sign into OneDrive and Sharepoint on the network, it doesn't impact those save locations.
I guess, though, I may as well start getting used to it. IT's official policy is that they're moving our network based "home drive" to OneDrive by EOY, and that they want to get everyone off of network based drives entirely and into Sharepoint by end of '21
I think OneDrive saves to Sharepoint in the background, so yes.
Our corporate IT is moving everything they possibly can to "The Cloud". Heaven help us when someone cuts the T1 line leading out of the main IT building.
we won't be able to go to the web site to report the issue, we won't be able to email them about it and we won't be able to call them about it because we're already on IP phones.
You cannot remove the "feature" to show recent folders when "saving" an unsaved document, without pressing F12 or having a QAB for the Save As dialog, to my knowledge. The features in the Options refer to what is displayed on that save-page
just googled that... apparently jerry nelson was only the voice; the same pupeteer does the body now as back then, Matt Vogel... the more you know star with rainbow trail
alright, off to take a 2-hr call and sit in a more comfy chair for the duration. have a good day folks!
Interesting. As I'm doing this refactoring, I've got a lot of broken code since I've moved properties from their original location to their new location but haven't yet patched up the call/usage sites.
RD, however, is happily parsing the code despite the fact that the code is uncompilable and it's doing so without the warning that the code won't compile.
Testing Question: I've got a class. It's got some properties and some methods. The theory on testing says that I create a RD testing module, create an instance of the class, populate the necessary properties with known values, call a method, then Assert if the method returns the expected result based on the known properties, right?
So you want to slow the opening of the host instead of slowing the opening of VBE?
I don't need it to open every time. For example, RD working in Outlook but I rarely use the Outlook VBE. The same could be said for any other host application that you aren't developing for.
@IvenBach well... I've already written the code, so I can't write failing tests first. Or do you mean something like x=5, y=6 then Assert x+y=10, then "fix" the test by Assert x+y=11?
When I ensure the test is failing Assert.IsTrue False 'actual where actual is a boolean variable. Once I see it fail then leave Assert.IsTrue actual to see it pass.
normally what they mean by failing test is set up the skeleton class or the interface so that the unit test will run but fail, then you write code. However, TBH, I have hard time doing that way because at that stage the class design is not fixed
Testing can get super crazy. You want to test for every possible thing that could go wrong. The problem is that if you knew all the things that would go wrong then your code would account for that already.
Therefore, for me, at least, it's important to write both positive and negative tests.
which then provides a good starting point. Once developed & established, then yes, you start writing failing tests for any bug fixes or enhancement going forward.
and in writing the code you only write enough to make the test pass. Then as other cases occur and the output isn't as expected, additional code is written to make that now pass; only enough to make it pass. In early development many things are known and individual tests are written to accommodate those knowns.
each one testing only one aspect of the overall expected results
I usually look for edge cases that I can write that cover the "in betweens"
@this quick question if you are here - do I need to inspect the parse tree to determine the context an identifier reference is used in or can I get it from the reference itself/something in DeclarationFinder?
or anyone else who would know
i have everything working in the inspection except the ability to filter out the acceptable uses of the class name we discussed yesterday
That is interesting: To the variable 'cus' of declared type 'MSACC.OLB;Access.CustomControl' a value is set assigned with the incompatible declared type 'MSACC.OLB;Access.Control'
Ah, I see - there's nothing that makes it obvious that one derives from other in COM. I get the same thing for other control types, It seems.
But I think this is wrong: To the variable 'IDbConnection_CurrentConnection' of declared type 'msado60.tlb;ADODB.Connection' a value is set assigned with the incompatible declared type 'ACEDAO.DLL;DAO.Connection'.
The code that raises the inspection above is:
Private Function IDbConnection_CurrentConnection() As ADODB.Connection
Set IDbConnection_CurrentConnection = CurrentProject.AccessConnection
End Function
The CurrentProject.AccessConnection returns a ADODB.Connection, not a DAO.Connection.
Public Sub t()
Dim x As Access.Controls 'CustomControls
Dim y As Access.Control
Set x = New CustomControls 'Implements Access.Controls, also has an enumerator
For Each y In x '438: Object doesn't support this property or method
Debug.Print y
Next
End Sub
if the x is dim'd as CustomControls, it works fine. Just not as the Access.Controls interface.
VBA Rubberducking
VBA Rubberducking