@Hosch250 sorry to hear that. My mum volunteers on a children's cancer ward - sees some very sad cases. But a lot do pull through. it's very tough on the families though.
Hey - I was reading on Pearson's site that Auto Instancing should be avoided Dim x As New y and AFAICT RD does not inspect for that...
reluctant to make a new issue for something I don't really understand so thought I'd mention it here first, of course I'll also check if it has already been flagged...
http://www.cpearson.com/excel/Classes.aspx NOTE: It is also possible to combine the two statements above into a single statement: Dim C As New Class1 This is called an auto-instancing variable. When the variable C is first encountered in code, a new instance is created. In general, you should avoid auto-instancing variables for two reasons: First, it adds overhead to the code because the variable must be tested for Nothing every time it is encountered in code. Second, you have no way to test whether a auto-instancing variable is Nothing because the very act of using the variable name in an …
Avoiding seems to make sense to me but not sure if there are any reasons why it could be a good thing, probably should be an inspection - can always disable.
I guess the reason for not auto instancing would be that the `Set x = New y` could be in an If statement and so potentially not used (therefore don't instantiate)...
> After reading here: http://www.cpearson.com/excel/Classes.aspx
I think a code inspection to detect Auto Instancing would be a good addition to RD...
```Dim x As New y``` apparently has these disadvantages:
- adds overhead to the code - the variable must be tested for Nothing every time it is encountered in code - there's no way to test whether a auto-instancing variable is Nothing because using the variable name automatically create an instance of the variable
other than that... I got myself a new harp yesterday, key of A. I can now play the first 80 seconds of Whammer Jammer, *almost* without running out of breath :)
*Scratches Head* - when I first tested I double clicked on each inspection result and am positive that the inspection did not show up. It's there now and I can't repro...
> The main point of this tutorial is that FizzBuzz is not at all trivial, but, many thanks to higher-order functions in Haskell, solvable. I don’t know about Java.
I don't remember how to do this offhand, especially since my brain is a trifle fuzzy ATM, but it should be as simple as something like seq.where (fun element -> element.Name.Equals "item") channelNode.ChildNodes
I wrote an app that pulls a MS Access DB into a DataTable and then displays it into a WPF datagrid. The dialog window has a search button which calls on a class that does the DB work.
The methods in play of the search window:
private void ExitBtn_Click(object sender, MouseButtonEventArgs e)...
there are so few post offices, that the ones that remain are busy. And they're not busy doing postage related stuff, because that isn't financially sustainable -they're busy selling stationery, selling insurance, processing social security paperwork, and selling overpriced pre-paid VISA cards.
@RubberDuck I can take a look tomorrow probably, I'm going to bed tonight (was just watching The Hobbit with the GF) and I have a party to go to tomorrow morning, but I'll be back home around 7 or 8.
@RubberDuck Only thing I'll say about that is that I've usually seen it written with the |> as the beginning of the next line in that type of scenario.
Apparently, reads 1 line at a time, then reopens to read next line, because backwards compatible to when DOS didn't have the memory to load a whole script
[retailcoder/Rubberduck]retailcoder pushed commit 3a81d2fa to rd-next: added RequiredLibraryAttribute class and implemented IInspection.Type property, to fix IgnoreOnce working off proxy types.
- Fixes a bug in `IgnoreOnceQuickFix` that made it not show up. - Enhanced `IgnoreOnceQuickFix`; fix is now disabled for project & module targets which can't be annotated. - Fixes a bug in About dialog causing GoFundMe link to navigate to rubberduckvba.com. - Inspection severity for `RedundantByRefModifier` is now `DoNotShow` by default. - Fixes `RedundantByRefModifier` tests which broke with `DoNotShow` severity. - Replaced "self-assigned" with "auto-instantiated
Last few days I've been reading and re-reading a truck load of VBA articles (prob half penned by you) and so just got up to this one: stackoverflow.com/documentation/vba/5351/…
I don't know if we should tell newbies to go to Up For Grabs.
That tag is usually only applied to issues that desperately need a fix and that aren't trivial to solve because they need a fix so bad they would be fixed if they were.
I think nothing is preventing you from creating actual WPF windows. We just have to use an ElementHost to make them play nicely with the rest of the VBE, in particular to make them dockable.
I wrote an app that pulls a MS Access DB into a DataTable and then displays it into a WPF datagrid. The dialog window has a search button which calls on a class that does the DB work.
The methods in play of the search window:
private void ExitBtn_Click(object sender, MouseButtonEventArgs e)...
VBA Rubberducking
VBA Rubberducking