@M.Doerner isn't that a separate concern? The parsing project should only deal with providing a service for writing to both code and to attribute, while the refactoring would choose to use that service?
@M.Doerner technically we could swallow all non-navigational keystrokes in code panes when a parse is running... but then, get that done wrong and the VBE is essentially bricked.. not sure it's a good idea
@FreeMan the fiery furry browser has a memory leak?
Now the proud owner of Classic Computer Science Problems in Python: https://www.manning.com/books/classic-computer-science-problems-in-python. Thanks, @ManningBooks #Countdownto2019
I love finding misunderstandings and misspellings for common idioms and phrases that totally change the meaning. Who knows others?
- The plot sickens
- Taken for Granite
- Escape Goat
- For all intensive purposes
- Piece of mind
- Peaked/Peeked my interest
- Nip It in the Butt
@Hosch250 I'll give you a like when you finish the book.
My recent experience has taught me it's much easier to buy the book than to read it. Entirely different again to understand and get the knowledge from reading.
@IvenBach Well, I'm 4 chapters into my Microservices book. I'll (almost) finish that one on my vaca.
I'm also 4 (smaller) chapters into my F# book (lots of small chapters there). Reading that one in snatches at work because I left my microservices book home for now, since I'm kind of busy.
I'll finish both of those first, then this one. Probably by June of next year, although might be longer, depends how many fires work manages to start.
@this I'm going to publish it on GitHub unlicensed for backup purposes, because if this works out, I might monetize it. However, I will license anything you feel would be interesting to you as MIT.
Depending on where I take this, I might even make (parts of) it open source under MIT.
I'm planning on turning it into a training tool, like how so many other language sites let you run the code right as you do the training.
@Comintern thanks for the rubberduck earlier - I now have something I can work with. I will come back to it tomorrow but I think I'm on the track to get the closed types registered by conventions.
Hi folks. Please, a little help with translations.
I pulled from `origin https://github.com/rubberduck-vba/Rubberduck.git (fetch)` Then opened the project in VS Added few lines of translations, modified other Cleaned the project Built the project Opened RD and I don't see the changes. What do I do wrong?
@SonGokussj4 @SonGokussj4 you said you did "fetch" - did you actually pull after you fetched? Fetching only updates the tags but pulling pulls the changes.
@Hosch250 Maybe you could demo that to the "I'm a beginner, but I'm writing an OS in VBA" guy
@Hosch250 needs to readjust thinking... Read that as "Piece of Crap" before realizing you meant "Proof of Concept". Brain has just not been right lately...
I'm having a brain dead morning so far... I start with:
Dim outputWB As Workbook
Set outputWB = Workbooks.Add
Then I do a lot of stuff (wide variety of routines called). At the end of all that, instead of blindly doing outputWB.Close, how do I check to see if the workbook is still open first so that the .close doesn't throw an error?
struggled to even put all that into words... May need sleep.
PSA: Take everything @FreeMan says today with a huuuge grain of salt. He is currently experiencing a major brain malfunction. Brain will be rebooted shortly.
Yes, that's it. After rebuilding it. I think it will be some stupid thing but don't know what.
My immediate git status is this
/GIT/Rubberduck$ git status
On branch next
Your branch is up-to-date with 'origin/next'.
Changes not staged for commit:
(use "git add <file>..." to update what will be committed)
(use "git checkout -- <file>..." to discard changes in working directory)
modified: Rubberduck.Resources/CodeExplorer/CodeExplorerUI.cs.resx
modified: Rubberduck.Resources/Inspections/InspectionNames.cs.resx
modified: Rubberduck.Resources/Inspections/InspectionResults.cs.resx
modified: Rubberduck.Resources/Inspections/InspectionsUI.cs.resx
@Hosch250 Mug was having a go 'round a week or two back with some guy who was asking a bunch of very poor, very vague questions about writing an OS in VBA. It was funny to me. Maybe I needed more coffee...
There's also a persistent misspelling I introduced into Rubberduck.SettingsProvider 3 years ago that I should fix at some point when it won't be obnoxious.
maybe need to run it through code analyzer? extension? something? that does spell checking. I wouldn't leave it in by default, though - as it might end up more obnoxious than the occasional typos that do make into the codebase.
@Hosch250 Probably in that a "VBA OS" would likely look just like that and wouldn't be able to do much more than what you displayed? (I just can't wrap my head around the idea of a VBA OS... How could that even remotely work? As a virtual machine maybe? You'd need a VBA host first, nonetheless. And that one wouldn't be in VBA...) Anyway, just my humble guess. ;)
As an old dog (age 73) learning new (Excel VBA) tricks, I am reasonably happy with putting together the code below. But I think it could be cleaner. How would you have coded it?
Private Sub Workbook_Open()
Dim lastRow As Long 'last row with data
Dim thisDate As Double 'start tim...
@Hosch250 I guess "as an example of something that's actually achievable". Dunno. brain's still non-functional today. It sounded good when I first typed it.
I.e., I'm allowed to purchase a million tickets, but it would take longer than the 4 days between drawings unless I was paying temp workers to go the convenience stores for me or something.
One time in the UK when the jackpot got silly-big, a consortium was trying to see if they could buy every permutation on the basis they were almost guaranteed to profit. IIRC it got denied because they weren't UK registered. They may have tightened up the rules by now.
@mansellan this! It might take so long to find the winning ticket in that pile that they'd no longer honor it. Is there a time limit to claim your prize?
Most of them go unclaimed for quite a while - it takes time to hire an attorney, set up a trust to accept the winnings, discuss the tax implications of the payout methods, etc., etc.
> Ticket expiration dates vary from 90 days to one year, depending on the selling jurisdiction. The expiration date is often listed on the back of your ticket. If the expiration date is not listed, check with your lottery. Unclaimed prizes are kept by the lottery jurisdiction.
> For `If` statements that are checking for strings, auto-closing quotes removes a space after the equal sign.
This: ```VBA If TestString = " ```
Changes too: ```VBA If TestString ="" ```
VBA auto fixes it to the correct `= ""` so it isn't the biggest issue, but still mildly annoying.
Version 2.3.1.4308 OS: Microsoft Windows NT 6.1.7601 Service Pack 1, x64 Host Product: Microsoft Office 2016 x86 Host Version: 16.0.8431.2329 Host Executable: EXCEL.EXE
> Tagging as a bug because this isn't the intended behavior, but given the caret is correctly positioned I'll treat this one as a lower priority issue; there's another SCP bug that's actually annoying and needs fixing - I'll try to slip a fix for both.
> Yes, this should be easy to update and a good first issue. Being a built in template, the source is stored in [this resource](https://github.com/rubberduck-vba/Rubberduck/blob/next/Rubberduck.Resources/Templates.resx). I am not certain if the annotation and the inspection needs any additional updates, however.
There is one more consideration not covered with the template. If you change the code in resource, how do you ensure that the file that was previously generated is updated? Though it
> Yes, this should be easy to update and a good first issue. Being a built in template, the source is stored in [this resource](https://github.com/rubberduck-vba/Rubberduck/blob/next/Rubberduck.Resources/Templates.resx). I am not certain if the annotation and the inspection needs any additional updates, however.
> Yes, this should be easy to update and a good first issue. Being a built in template, the source is stored in [this resource](https://github.com/rubberduck-vba/Rubberduck/blob/next/Rubberduck.Resources/Templates.resx). I am not certain if the annotation and the inspection needs any additional updates, however.
> As realized in the comments in #4622, a simple versioning system may be needed for the built-in template in order to support the scenario where we need to update the built-in template's code in the resource. That also implies prompting the user whether to update the built-in template as they may have already made customization to the template and may not want to lose the changes.
My guts is that VBE won't care about that; it will always be looking for CLSID keys.
@Comintern Consider also that even if there's a DLL, it doesn't mean it's all A-OK; it might be out of date, corrupted, wrong bit, etc. etc. -- I think actually loading it via an object instantiation is the only way to be 100% sure.
> IMO versioning is overkill. If you added an earlier version of a template, it's in your project already; adding another instance will use the newer template, and that's fine. Why would a template change anyway? Adding annotations? They can be added later on, inspections can even find the missing ones, at least in the case of @PredeclaredId.
> No, the issue is that when we first add a component, the subsystem will check the `%APPDATA%\Rubberduck\Templates` for a `rdt` file of that template. If it doesn't exist, it will create a new `rdt` file from the resource file.
So if we issue an updated version where we changed the template, the users who already generated the template `.rdt` file wouldn't get the changed template unless they delete that file in which case we will then regenerate from the resource file.
> No, the issue is that when we first add a component, the subsystem will check the `%APPDATA%\Rubberduck\Templates` for a `rdt` file of that template. If it doesn't exist, it will create a new `rdt` file from the resource file.
So if we issue an updated version where we changed the template, the users who already generated the template `.rdt` file wouldn't get the changed template unless they delete that file in which case we will then regenerate from the resource file.
> I'd say just list everything that's available; you want to use the file from 3 releases ago, go ahead. Perhaps include a readme.txt in the templates folder, suggesting a naming scheme: rd.template-name.rdt for the "built-ins" (gets overwritten), and user.template-name.rdt for customized ones.
1) in future, users would be able to create their own templates for where there is no corresponding built-in template. Labeling them as `user.template-name.rdt` seems a bit silly. We can use the convention of `template-name.rd.rdt`, and say that those will be always overwritten by RD which... 2) means the user needs a way of knowing there's a new version of the built-in template that won't be picked up because their customized template will be a
Just as an aside, I'd use a term like "Custom Template" instead of "User-Defined Template" to avoid future confusion when we start abbreviating it to UDT.
@MathieuGuindon ah, and I was thinking that if they customize the built-in template, they simply edit the rdt file for the Predeclared Class Module
and that menu entry will then use that file with their customization
but if you want to say that they should not customize those files but rather create their own file and call it My predeclared class module, which then appears as a 2nd menu item, we could do that.
I think it could be fairly simply implemented... the .rdt files that ship with RD 2.4 are the files they are; if RD 2.4.35 changes foo.rdt and user had the version we shipped with RD 2.4.27 and tweaked it, we have all rights to overwrite it when 2.4.35 is installed - but we should not delete any .rdt file that we're not shipping/installing
As an old dog (age 73) learning new (Excel VBA) tricks, I am reasonably happy with putting together the code below. But I think it could be cleaner. How would you have coded it?
Private Sub Workbook_Open()
Dim lastRow As Long 'last row with data
Dim thisDate As Double 'start tim...
VBA Rubberducking
VBA Rubberducking