@MathieuGuindon is it taboo to have a command behave differently base on a condition? Is it better to have 2 explicit commands do and addition/removal?
I’ll try and get a PR submitted by tonight to elaborate.
Don’t know how you manage such —-long winded—- descriptive answers on your phone Mug.
Coming from an Excel-VBA background I'm having a hard time wrapping my head around what the best way to convert code that I'd typically write using resume as try/catch/finally(TCF) blocks instead.
I know TCF can speak to a multitude of languages; however for the sake of illustration and hopefull...
> Close #2964. TODO: - Create discrete separate command for Ignore/Unignore that will add/remove the annotation respectively. Following this train of thought there shouldn't be any sharing for properties, one for each (IE ExecuteToggleTestAnnotationCommand needs some love). - IsSelectionATest is a lie. Make it check what it's claiming. Question: - Is how I've done the visibility within the XAMl for TestExplorerControl appropriate? I thought about having it be a property on the VM but...
that didn't feel right when I was trying to code it up.
> # [Codecov](https://codecov.io/gh/rubberduck-vba/Rubberduck/pull/5064?src=pr&el=h1) Report > Merging [#5064](https://codecov.io/gh/rubberduck-vba/Rubberduck/pull/5064?src=pr&el=desc) into [next](https://codecov.io/gh/rubberduck-vba/Rubberduck/commit/bdaf6d7be446e9ca2814b1fdf2503143f6dafe38?src=pr&el=desc) will **decrease** coverage by `0.05%`. > The diff coverage is `35.29%`.
> # [Codecov](https://codecov.io/gh/rubberduck-vba/Rubberduck/pull/5064?src=pr&el=h1) Report > Merging [#5064](https://codecov.io/gh/rubberduck-vba/Rubberduck/pull/5064?src=pr&el=desc) into [next](https://codecov.io/gh/rubberduck-vba/Rubberduck/commit/bdaf6d7be446e9ca2814b1fdf2503143f6dafe38?src=pr&el=desc) will **decrease** coverage by `0.05%`. > The diff coverage is `35.29%`.
as a RubberDuck newbie (a few hours) I wonder what I need to do to come from the code inspection window to the source line in error, or even the SUB / FUNCTION involved.
In some instances I see on the RD workbar "n references" and those help, but . after I fixed the problems referred there . pressed refresh there still **are** many errors but no "references" The module has over 1400 lines, maybe I should start with a smaller module?
> Welcome to the RD family. You'll soon wonder how you ever lived without it!
In the _Code Inspection_ window, double clicking on an inspection should take you directly to the offending line of code. If it's not, then there's definitely a bug that you can report.
My Code inspection window was overlaying the sourcecode, So I clicked and clicked and did not see anything happening. Was expecting the target window would come to the front.
Thanks for the warm welcome (36 Celsius here) and the perfet answer. Bert
My Code inspection window was overlaying the sourcecode, So I clicked and clicked and did not see anything happening. Was expecting the target window would come to the front.
Thanks for the warm welcome (36 Celsius here) and the perfect answer. Bert
@Duga "Was expecting the target window would come to the front." Can that be made to happen, or is it "the VBE's already on top of the z-order and can't be any more on top"?
which is kind of awkward. IDK about you but I usually have the main area maximized
and my other stuff docked to sides.
never saw the point in windows-in-a-window, TBH.
Unfortunately, like Bert, I usually have the CI TW as a popup because otherwise docking it would just squeeze everything else out so I deal with the annoyance of manually moving the window when it's in way which it almost always manages to be. :\
CE to the right, Immediate on the bottom, Timepieces and Localsgloating floating on the other monitor. If most/all of those could be tabbed in one docable window (or maybe 2 - CE is best displayed vertically, the other 3 are best horizontal), that would be the bee's knees!
CI, ToDo, etc are opened and floating on the 2nd Monitor as necessary...
gutten morgen, @Mug!
wait, should that be gutten morgen, @Stein for the full translated effect? :)
and also because I usually am opening/closing files as I change projects and I don't always need to parse.
so yes, it's too long.
sometime I try to sneak in a parse while I work on other things in foreground but it can also kill when doing several changes to objects (e.g. importing a number of objects)
Also, I have a dickens of a time getting things to dock where I want them. How do I make the horizontal Immediate window shorter so the CE goes all the way down. How do I get Properties to dock to the right side, below the CE instead of next to it and full window height?
Don't use Code Metrics 'cause I don't know what they mean. Probably need a whole duckin' class on that...
@MathieuGuindon it also help to pay attention to the thin gray highlight. It's nowhere as obvious as VS' docking UX, but it does make a distinction between "dock to bottom of this particular window" vs. dock to the bottom of the main window"
> Thank you @BertLindeman, don't hesitate to ask *anything* about using Rubberduck!
A few tips with inspections:
- At this point the resolver isn't "seeing" MSForms controls' default interfaces (i.e. we only see a `Control` when we're looking at a `TextBox`). This makes "procedure not used" fire false positives for most event handlers - you'll want to `@Ignore` those. - Same with document modules; we see the members defined by user code in e.g. `Sheet1`, but at this point the `Worksheet
> **Rubberduck version information** ``` Version 2.4.1.4795 OS: Microsoft Windows NT 10.0.17763.0, x64 Host Product: Microsoft Office x86 Host Version: 16.0.11328.20368 Host Executable: EXCEL.EXE ```
**Description** Recently when adding a new module with the Rubberduck Code Explorer, it's been leading to some error messages and unresponsive behaviour. Basically, the mouse turns to a blue circle, and after a minute or so (following the adding) I get a
select p.Id
, p.Score
, (select * from Posts p1 where p1.Id = p.ParentId) Tags
into #answers
from Posts p
where p.OwnerUserId = @userId
and p.PostTypeId = 2
> > Rubberduck has a number of features that are awesome, but hard to discover. Everything you can do with _annotations_ is documented [here](https://github.com/rubberduck-vba/Rubberduck/wiki/Using-@Folder-Annotations) and [here](https://github.com/rubberduck-vba/Rubberduck/wiki/VB_Attribute-Annotations) in the wiki (which is fully open BTW - feel free to add more content!).
Thank you. Those tips are worth so much. Will study after temperature drops a bit.
The math solution is, to find out properties of the things we work with, and prove those. Then we re-search those properties for more properties we can now prove. And on those more intricate properties, we build even more complex proofs.
In the case of your parking lot, the mathematician might s...
@FreeMan While here are you learning and able to perform your tasks more efficiently?
If the tasks get done adequately I don't think managers/bosses usually care. And if you're making things better in the process and they can see that via results all the more reason to #Lurk in chat and SE.
> **Justification** It's habit for me to use the hotkey `Esc` to dismiss as title states. Some windows are dismissable while others aren't. Unify the UX with respect to the UI windows.
**Description** - If a window is not docked, IE free-floating, and has focus it should be dismissable with `Esc`. - Free-floating and doesn't have focus `Esc` shouldn't dismiss it. - When docked `Esc` shouldn't dismiss, It should remain docked.
**Additional context** Dismissable via `Esc`: - Settings
Good thing that the only thing this displays is company perks (5% off $50 or more purchase at Target. Wooo!) and the only personal data they have is my work email address.
I don't know about the rest of programming world but in Access there is a further difference between a modal form and a dialog form.
from user's POV a modal form and a dialog form are one and the same
but from programmer's POV, they aren't - with a dialog form, the code won't return until the dialog has been dismissed whereas with a modal form, the code returns immediately after opening the said form.
But I don't know if that's just a Access quirk. Never tried to implement a dialog in C++ and I don't recall C# having the equivalent of a modal form.
> **Justification** We want to put our best webbed foot forward. Having a non-standard window presentation makes Rubberduck look like it's made by volunteers.
**Description** Standardize ducky icon to corner of all windows: {Ducky.ico} {Rubberduck} - {WindowName}
@Duga "Having a non-standard window presentation makes Rubberduck look like it's made by volunteers." But, RD is made by volunteers. At least, that's what I've been told...
i also am convincing the engineer in charge of the labview program thats running tests on our newer test equipment to dual write to the old access table and a new SQL Server table
as a transition since the older C++ applications are... indecipherable
plus it would be difficult to get something to recompile the oldest copy that runs on win98
> # [Codecov](https://codecov.io/gh/rubberduck-vba/Rubberduck/pull/5064?src=pr&el=h1) Report > Merging [#5064](https://codecov.io/gh/rubberduck-vba/Rubberduck/pull/5064?src=pr&el=desc) into [next](https://codecov.io/gh/rubberduck-vba/Rubberduck/commit/bdaf6d7be446e9ca2814b1fdf2503143f6dafe38?src=pr&el=desc) will **decrease** coverage by `0.05%`. > The diff coverage is `35.29%`.
> # [Codecov](https://codecov.io/gh/rubberduck-vba/Rubberduck/pull/5064?src=pr&el=h1) Report > Merging [#5064](https://codecov.io/gh/rubberduck-vba/Rubberduck/pull/5064?src=pr&el=desc) into [next](https://codecov.io/gh/rubberduck-vba/Rubberduck/commit/bdaf6d7be446e9ca2814b1fdf2503143f6dafe38?src=pr&el=desc) will **decrease** coverage by `0.04%`. > The diff coverage is `38.3%`.
> # [Codecov](https://codecov.io/gh/rubberduck-vba/Rubberduck/pull/5064?src=pr&el=h1) Report > Merging [#5064](https://codecov.io/gh/rubberduck-vba/Rubberduck/pull/5064?src=pr&el=desc) into [next](https://codecov.io/gh/rubberduck-vba/Rubberduck/commit/bdaf6d7be446e9ca2814b1fdf2503143f6dafe38?src=pr&el=desc) will **decrease** coverage by `0.04%`. > The diff coverage is `38.3%`.
Isn't openpyxl documented anywhere? Certainly you can parameterize a Python script, kind of like you'd parameterize a PowerShell script? Curious what Python does that VBA can't do, this feels like "with enough duct tape, it'll work". Not familiar with Python, but why would you need to load_workbook if Excel is already there with the workbook opened and its VBA code running? — Mathieu Guindon15 secs ago
maybe one day there will be a valid reason to automate Excel with Python. until I see it, I'll keep the opinion that Python-integration fans are just VBA haters that can't be arsed to write the VBA code to do their thing.
@Hosch250 I'm not sure if I can achieve that. There's Interaction.Behaviors in the XAML. As I don't know what those are I'm unable to get search results.
VBA Rubberducking
VBA Rubberducking