> If there is any truth in product development, it would be that a good product fulfills a need, even if that need is entirely made up and supplied to the consumer. Advertising creates a hole, then a product fills it. Want to feel pretty? Buy shampoo. Dead-end job got you down? Eat at Chili’s. Trapped in a loveless marriage? Buy a bow-wrapped BMW.
Does this also apply to RD?
> Crappy code with bad indentation? Unqualified cell references abound? Implicit member access got you in the dumps? We’ll fret no more friend because #Ducky has got your back. No more will these problems plague you and your team. Properly indent without worry. Appropriately qualify Range object with their respective Worksheets. And these unsightly implicit method calls will be highlighted by AvalonEdit. #ComingEventually
This code checks if "B2" and so on is filled in and if it is then it will generate a new ID number for the row of data that was transferred to the worksheet on the next empty row, I know this code creates opportunities for bugs so I want to make it better but I don't really know how I could do it...
@this Dunning-Kruger. The tendency of incompetent people to overestimate their competence, due to their incompetence in estimating ability.
from the wiki:
> In 2011, David Dunning wrote about his observations that people with substantial, measurable deficits in their knowledge or expertise lack the ability to recognize those deficits and, therefore, despite potentially making error after error, tend to think they are performing competently when they are not: "In short, those who are incompetent, for lack of a better term, should have little insight into their incompetence—an assertion that has come to be known as the Dunning–Kruger effect".
dealing with one of those was my life until recently...
I love that RD recognizes that I've open a new Excel file and kicks off a parse, but if it's an XLSX that I've just opened, there will be no code in it (by definition) and there's no real need to parse it.
If I'm adding code to an existing XLSX and I want it to parse, I should Save As first so that it's an XLSM, then let RD do its thing.
I often have an XLSM open, then have to open a bunch of XLSX files for other fires before getting back to my code. The frequent reparses slow things down, and sometimes I'm jumping from code to XLSX and back, and it takes time to find my code amidst all the non-code files that are opened
Maybe group XLSX at the bottom of the CE so they're there, but out of the way?
@MathieuGuindon or... select the (new) "Show all" CE toolbar item, ignored projects show up as ghosted-icon nodes. Right-click the relevant one -> Unignore.
Customer: My engine does this noise only some times.
Mechanic: Any pattern to when it occurs?
Customer: Uh... No.
Mechanic: It's going to take a lot longer than you think to diagnose.
^ Had that several times at a previous place I worked.
Mechanics testing for 3 days couldn't find anything. Called and told customer who came and took a mechanic for a 30 min drive. Nothing. They said they'd bring it back next time it happened and left. ~10 mins later "You already knew it'd happen when I left and stop just before I got back." "Yep. We'll look at it again."
Yeah, nothing more less fun than intermittent issues. :( At least with mechanical stuff, you can grab your phone and get a video including any dash indications and capturing (somewhat) the noises. Not so much for buggy software...
> @Inarion You are correct, I am _not_ getting the dialogue opening behind other windows. (Just ran into this again today and thought to search for the issue instead of blindly opening a new one.)
Additionally, I'm actually getting an error in the log in reference to the 'AddRemoveReferencesPresenter', so it seems that it's an actual issue, more than an annoyance (which opening behind everything else certainly is).
@FreeMan that might have something to do with RD TLB listed twice
why is the RD TLB referenced anyway?
IIRC this does cause problems
...it's also why we spliced the unit testing API into its own TLB
ok this is driving me nuts. why the hell would =INDEX(NamedRange,1) work fine, but =INDEX(INDIRECT("NamedRange"),1) not work at all and yield a #REF! error?
like, I've been doing this for ages, and just now, suddenly, it refuses to work
@Vogel612 When a repo branch is deleted I know you can run git remote prune -n remoteName to do a dry-run and list what will be pruned. I've already done that and actually ran the command. I still have the local branch FileDialogExamples. Is it status-by-design that the local branch remains and isn't removed as well?
@Vogel612 & @retailcoder : (as a reference) in mzTool there is properties helper. [https://www.mztools.com/v8/onlinehelp/MZTools8Help.html?new_method_property_assistant.htm](https://www.mztools.com/v8/onlinehelp/MZTools8Help.html?new_method_property_assistant.htm) We declare property name, type and private property name, pick GET/SET/LET'ers. It works nice for a single property per step. It produce code like this.
TirNoPer360 = Opt(sum)? Your question is extremely unclear / hard to understand. I second @BigBen in requesting that you edit your post to clarify how Opt relates to the other function, since right now it reads essentially like "I have an apple and a banana, how do I get a banana-flavored orange by eating an apple". — Mathieu Guindon44 secs ago
slightly annoying when OP doesn't actually read the dupe target:
Not duplicate because im testing it in a sheet that only has the value that im looking for. And already tried the If Not Rango is nothing And since here the find will always be succesful i didnt need to add that. Also for some reason its adding numbers in certain cells idk why. — Armas.Chuy14 mins ago
@FreeMan think I should rollback the edit to the unqualified Cells?
cause since OP edited it's effectively a new question, with a problem of "it's not working"
I'm not sure now. It's one of those questions that OP has fixed the original problem by editing, so all we've got is "it's not working"
It will never be in column A simply because the format on the original code will be always at least on column B. Right now im doing it on column D on the test sheet. Btw now the 1004 error is not appearing but its still not working :( — Armas.Chuy8 mins ago
maybe optimally it should be deleted and a new question asked.
yeah. chameleon questions with an entitled OP that doesn't understand their own code but knows what's right and what's wrong with it (geez why are you even asking then?), are the worst.
My code parses through a contiguous range of data in a spreadsheet (orng) and creates subranges from orng that contain the same string value (lot number) in the 6th column of orng. orng has 42 rows and 38 columns and each subrange has 1-15 rows and 38 columns. As far as I know, I can't create a n...
@Vogel612 & @retailcoder : (as a reference) in mzTool there is a [properties helper.](https://www.mztools.com/v8/onlinehelp/MZTools8Help.html?new_method_property_assistant.htm) We declare property name, type and private property name, pick GET/SET/LET'ers.
It works nice for a single property per step. It produces code like this.
``` Private _fooBar As String '_ is default prefix
Public Property Get FooBar() As String FooBar = this.F
@Duga am I the only one thinking the MZ dialog approach is rather.. heavy-handed?
like, I'd much rather have a more R#-like approach, as suggested in the OP. the private type has all the metadata we need, if we assume generating Property Get and Property Let/Set for all UDT members is good-enough.
Looking back, the concept of Public vs. Private was intuitive enough but I was used to simply peeking inside various internals that it was an hindrance in properly groking the abstraction.
Hey just a heads up, there’s a small reddit thread going on about Rubberduck right now, some users bringing up some feature requests: reddit.com/r/vba/comments/cbh8s6/…
and the person saying only the indenter is useful and nothing does anything is... missing out.
2
> Seems like overkill for a language which is incredibly simple to learn, use and debug.
So you think, buddy. So you think.
> It feels like Rubber Duck is in a weird place, since once you start needing an addon like that you're probably at the point where you should be moving away from Excel/Access into a more Robust Language.
VBA Rubberducking
VBA Rubberducking