Hi all. Just got back to VBA after a bit of a hiatus. But now when I start VBA, RD says it threw an unexpected exception and to check the log. This happens in all MSO apps. I checked Process Explorer for sneaky instances of MS apps or RD (like automation), but there are none. Where is the log is says to check..? Any suggestions..?
No, there have been no updates or changes to MSO or RD. Oh...this isn't the usual case of conflicting duplicate Autosave workbooks...that I know how to deal with.
@spinjector Not guaranteed, but I'm 99.99% sure that an update to the latest pre-release build will keep all settings. There are some new ones since 2.2 (current build is 2.4.1.5196, after all!), so I'd suggest taking screen shots of your current settings, then taking a wander through the new settings. Make sure nothing has changed, tweak the new ones to your desires
#DontFeedTheTroll
@spinjector Oh, and, welcome back!! It's good to see Max in the room again
@FreeMan haha thanks =-) the company i work for is being sold, and my work is all upside down and i've been doing more SQL than VBA, to export sales & financial history for the new company...
yes in a way... family owned company... patriarch passed away, kids started running it into the ground, more interested in the short-term money than actually working to keep it healthy & profitable in the long run...
so onwards & upwards, trying to find another job as the MSO & VBA guru, hopefully with SQL too...
ok i have the 2.4.1 installer, so i just run that to install over the existing one..?
that sucks... i worked for Corel when they bought InfoCentral for the sole purpose of killing it in favor of their extensively hard-sucking address book turd... people were calling for support with exploding heads because their entire lives were neck-deep in IC...
At least MS, when they buy something now, typically ends up keeping it around at least for a while.
Thinking of Wunderlist (which got rewritten as MS Todo with basically the same UI) and Newtonsoft Json (which got rewritten and integrated directly into .NET as System.Text.Json).
And GitHub is actually expanding in quite some awesome ways.
I wouldn't be surprised if they eventually shut down Azure DevOps in support of it.
@MathieuGuindon This isn't a good answer, but I don't think it's a non-answer:
I'm not as far ahead as all that, i barely even have a handle on Git, lol... but i probably should since i'm looking at programming jobs too... thing is i've never worked in a pure programming environment tho....
I couldn't quite find the answer to my question, but if there is another post I am missing, please, let me know. I am trying to add values to a dynamic array using range.value. The problem is that the cells I want to add to the array are not adjacent/contiguous. The array is created but it is onl...
hmmm i've been saying for a year now i need to start digging into RD to see if i can contribute, perhaps i should do that and to learn git at the same time...
oh, today's news here - something blitzed my current install of RD, couldn't install and couldn't uninstall any version, so i let the windows programs window clear it out, then reinstalled my current version with the intention of uninstalling it right away so 2.4.1 could go in, but then i found the current version is working fine again, even the log file is getting updated...
@Hosch250 I would have converted it to a comment, but Vogel already deleted it. Back when 200 was a mod, that would have probably flown as a "poor answer"
Ok so flip it... ghost that Win10 into a vdi on a backup drive, then wipe the primary drive, install ubuntu, then vBox, then put the Win10 in a vm... =-)
nope. i use msforms, vbide, regex, etc, just removed a couple, re-added them, and they're still gray, in fact, now they've all turned gray, none are black any more...
@spinjector IIRC the nodes are usable before identifier references are fully resolved, so nodes might only turn gray after that's completed.
@mansellan on one hand I like non-actionable nodes being grayed out. On the other hand I'd kind of expect libs I'm not using to show up grayed out too... that's probably an interesting question to ask on UX.SE
I'm sorta glad I didn't let myself see the high quality light saber. My inner nerd would have screamed "All your saberz are belong 2 me!" and rationality would have went out the window.
As we're approaching the release date for v2.5.0 of Rubberduck (an open-source VBIDE add-in), we're facing a bit of a dilemma regarding a specific type of tree nodes in one of our toolwindows:
The idea is to show library/project references in the treeview, and somehow convey whether a particul...
well, the semantic point is that you cannot make a person not read something; unless you have a grouping that says "not in use (4)" and is collapsed and a group that says "in use (1)" which is expanded, where the IDE moves items, you don't have a way to not make the user read it wihtout them explicitly digging4
one thing that makes me wonder, is why stdole and office libraries are grayed-out in an empty project. they're not locked, and they're not in use AFAICT.
@this i'm jumping on that bandwagon, as it seems like a simpler approach. not actionable italicized. yo ucan't make someone not read, but you can make a visible difference where they will need to know something about layout
the javascript guy made it; was trying it out to see if it's better than trying to configure ublock origin and privacy badger on chrome
and on that note, taking car to the shop to get a chip filled (warranty = free) then home to play some RDO before i have to pick up the kids from daycare
Hmm, I definitely think that greyed-out (no other adornements) should mean unused - that seems to be idiomatic to me - e.g. unused procedures in VS get dimmed (is that R#?)
I can see why that'd be useful. Few times we've had to deal with some stupid legacy activeX control that nobody should be using anymore so it was a fun scavenger hunt....
In VS (especially with the SDK format) I can see at a glance what I'm depending on
by category
Unrelated: is it worth raising issues for stuff that needs AvalonEdit, or should I just suggest it here?
@this Conceptually, a control is just a type from a COM library. We list DLLs under references, but not OCXs, even though they're different flavours of the same tech.
Granted, they're added in different ways, but still.
@this I wonder if that's because OCXs are also COM DLLs, and you can use them as such so long as they're referenced (from standard modules say). But forms also ref them directly for their control types...
To sum it up, I think the only thing that is surprising about the greying out behaviour of the references in the CE is the bug that freshly added references show as not greyed out initially.
There's still the matter of the unused references looking the same as the locked references, though. Granted, they have different icons but I have to squint a bit to see it's a padlock so...
@M.Doerner there are two pretty reasonable user expectations about greyed-out nodes: 1) actionnable nodes are black, non-actionnable nodes are grey (current intended behavior), and 2) unused reference nodes (i.e. actionnable) are grey, used refs are black. Both are defensible expectations, and they're contradicting.
fwiw, when I think of the conjunction of "Greyed out" and "Non-actionable", I think of action targets - buttons, menu items. In on-screen items (lists, code), I don't automatically think greyed = non-actionable.
but you can't directly remove a greyed list item. you have to interact with it (e.g. right-click), at which point the menu item is either greyed on just not there.
It's the difference between "immediate action" and "secondary action"
greyed to me just means "nothing useful here"
buttons and menu items are first-order - when you click them you expect something to happen, so greying out means "it won't".
list items are second-order, you have to choose an action for them
As we're approaching the release date for v2.5.0 of Rubberduck (an open-source VBIDE add-in), we're facing a bit of a dilemma regarding a specific type of tree nodes in one of our toolwindows:
The idea is to show library/project references in the treeview, and somehow convey whether a particul...
VBA Rubberducking
VBA Rubberducking