> Oh.... have just discovered that this impacts MS Word but NOT Excel on the same computer.
Also plan above has been foiled... on two counts...
1. Apparently reinstalling (resetting) Windows no longer fixes the issue 2. I set logging to Trace but so far the log folder remains empty
When I tried to open the log files via the Settings UI I kept getting something that amounted to a Folder Not Found error. I created the folders manually but...
> Oh.... have just discovered that this impacts MS Word but NOT Excel on the same computer.
~Also plan above has been foiled... on two counts...~
~1. Apparently reinstalling (resetting) Windows no longer fixes the issue~ ~2. I set logging to Trace but so far the log folder remains empty~
~When I tried to open the log files via the Settings UI I kept getting something that amounted to a Folder Not Found error. I created the folders manually but...~
> I think it may help to note that the settings for the docking and the window positions of toolwindows within VBE are maintained by a registry key (keys?) that is managed by VBE, not by Rubberduck. For that reason, uninstalling & reinstalling will have no effect because the keys are persisted and VBE associates the positions to the GUIDs of the toolwindows.
In a dire situation, the option is to delete/rename the registry key `HKEY_CURRENT_USER\Software\Microsoft\VBA\X.Y\Common\Dock` where `
@Duga I've largely reverse engineered the binary format of that registry key. Rubberduck could perhaps take a snapshot of that key at startup (IIRC, it's only updated when quitting the host application), and then at least a user would have the ability to roll back without losing all of their customisations. Or, given we know the binary format, we could potentially edit the .reg file on the fly, and restore selective window states.
We could even remove the RD windows from that key as part of the uninstall process.
And/or add better RD window states as part of the install process.... Otherwise, on first use, the size/visibility/position of RD windows is pretty poor, by default
::45431974 there's an enhancement issue for adding ToolWindow "workspaces", but while I think I know how to manipulate the registry key, the changes are only effective after a restart of the VBE. I suppose that's better than nothing, but ideally we'd work out a way of repositioning windows dynamically... It's just that VBIDE doesn't expose any methods for doing so.
@MathieuGuindon I took this comment for granted but am now ruminating over it. Sorry to be a pain... why is VarType more robust than TypeName when parsing a JSON object? I said dictionary originally. That was the JSON object being returned and nested within that were different datatypes I need to handle differently so was using Select Case TypeName(dict(currentKey)) to branch the code to handle different datatypes accordingly.
I have been reading this but ended up more confused as this seems to say, in my instance, that I will get more useful information using TypeName than using VarType for handling the potential datatypes within the JSON. Or have I misunderstood?
I am thinking specifically of a Collection object. TypeName will tell me it is a "Collection" so I can loop to foo.Count. If I use VarType and get vbObject how would I then know how to handle it properly? Is it just because I am focusing on too specific a case and not in wider VBA terms?
Ok, so the JSON is basically irrelevant here since you already have a VBA object.
As the answer to the SO question you linked already states, VarType is preferable as long as you know that the type you are looking at is not an object type.
This function cannot tell you which kind of object you are looking at, it just knows that it is an object.
@QHarr TypeName will tell you Collection but you can't know for certain that it's a VBA.Collection. what happens if you have a Collection class in your project, or another library? The only way to be sure, is to first check var is an object and then check TypeOf var Is VBA.Collection
Unfortunately, it seems to have the quirk that it will return the type code for the return value of the default member as long as it is parameterless, I think.
Note that the default member of Collection has a parameter. So VarType should return vbObject.
Hm, to check whether you are looking at an object, you should probably use IsObject.
So, to sum it up. First use IsObject to see whether it is an object or not. Then use a select on VarType in case it is not an object or select using TypeOf in case it is an object.
@M.Doerner I think IsObject is just a convenience wrapper around vartype, but yes, might as well use it and make your intentions clear, and avoid the parameter issue altogether.
But imagine you're using Excel, and you have a reference to Ms Forms. You pass a textbox object to TypeName and it tells you "Textbox". How do you know if it is an Excel.Textbox or a MSForms.Textbox?
I am getting RD has caused an Access Violation. Remove it from available add-ins. I can't find this mentioned in issues - with a simple search of is:issue is:open Access violation
It repeatedly happens in workbooks I have powerquery scripts in.
Grrrr...... I can't add a powerquery to anything now without access violation message re RD. Why now? Is this to with later version? I may need to try with earlier version.
@QHarr which version of Excel are you using? IIUC 2016 has a COM add-in for Power Query, and prior years has an Excel add-in.
I could be completely wrong. The best thing to do will be to check the logs. Lots of things can cause Access Violations, but this seems specific to PowerQuery. Some of those VBA calls and scripts have a lot of parameters and special characters. It could be that you've found a parser bug.
or, it may be some awkward clash for resources if RD and PowerQuery are trying to refresh at the same time. But it is strange that you've only just started experiencing this, and that others haven't reported it (yet?)
Entrevue/podcast en Français sur Rubberduck avec Mario Cardinal et @GuyBarrette pour le Visual Studio Talk Show ce soir! #MVPBuzz #CDNMVP
French interview/podcast about Rubberduck with Mario Cardinal and @GuyBarrette for the Visual Studio Talk Show tonight!http://visualstudiotalkshow.libsyn.com
I wonder if it's possible to make a Batch Script to execute the following:
Execute a command like ping -n 3 127.0.0.1 (or other command) and if the command was execute successfully blink the CAPS LOCK LED 2 times but if the command was't executed successfully then try to execute again. And if th...
If anyone's ever had issues with using an ElementHost in WinForms and black areas when resizing I'd be pleased to know :) Even more so if you actually managed to fix it
VBA Rubberducking
VBA Rubberducking