function Add(out SourceType: XlListObjectSourceType; out Source: Variant; out LinkSource: Variant; out XlListObjectHasHeaders: XlYesNoGuess; out Destination: Variant; out TableStyleName: Variant): ^ListObject; stdcall;
apparently the clr even offers a debugger + profiler? maybe we could hook into the VBE a new window and run it with CLR and somehow control excel with interop or whatever?
could even extend vba this way, add features the clr offers perhaps
@Comintern were you looking for examples of strongly typed object from variant? This gets strongly typed from IUnknown...
Option Explicit
Private Declare Function SendMessage Lib "user32" Alias "SendMessageA" ( _ ByVal hwnd As Long, ByVal wMsg As Long, ByVal wParam As Long, lParam As Any) As Long
Private Const WM_USER As Long = &H400 Private Const EM_GETOLEINTERFACE As Long = (WM_USER + 60)
Sub test()
Dim oUnknown As IUnknown Dim oTextDoc As tom.ITextDocument
Dim ret As Long
'Insert the hWnd of a RichEdit here Const hwnd As Long = &H190F2E
ret = SendMessage(hwnd, EM_GETOLEINTERFACE, 0, oUnknown) Set oTextDoc = oUnknown
@Hosch250 we'll do it with TeamViewer on my end, the admin credentials might authorize access to, well, my credit card account and the whole renewal stuff
A first chance exception of type 'System.IO.DirectoryNotFoundException' occurred in Rubberduck.VBEditor.dll
A first chance exception of type 'System.IO.DirectoryNotFoundException' occurred in Rubberduck.VBEditor.dll
A first chance exception of type 'System.IO.DirectoryNotFoundException' occurred in Rubberduck.VBEditor.dll
A first chance exception of type 'System.IO.DirectoryNotFoundException' occurred in Rubberduck.VBEditor.dll
A first chance exception of type 'System.IO.DirectoryNotFoundException' occurred in Rubberduck.VBEditor.dll
debug output is literally filled with those
all that throwing and catching is a bottleneck
that one's rather interesting:
2016-05-26 22:02:29.1421;TRACE;Rubberduck.Parsing.Symbols.IdentifierReferenceResolver;IdentifierReferenceResolver/Default Context: Failed to resolve True. Binding all successfully resolved expressions anyway.;
So all the System.IO.DirectoryNotFoundExceptions come from this line of code: return Path.GetFileName(project.FileName);. Why is that being shoved through Path.GetFileName?
Please tell me it isn't just to parse it.
Nope: `FileName = '((Microsoft.Vbe.Interop.VBProjectClass)(project)).FileName' threw an exception of type 'System.IO.DirectoryNotFoundException'
What's messed up is that the Saved property is true for a completely empty document.
I'd say it's misnamed.
I think I have it. If the project.BuildFileName only contains a file (i.e. VBAProject.DLL) then it hasn't ever been saved. If project.BuildFileName contains a path (i.e. 'C:\Dev\Book1.DLL`), then project.FileName shouldn't throw.
2016-05-26 23:43:56.5199;TRACE;Rubberduck.Parsing.Symbols.ProjectReferencePass;Built-in project references linked up in 12ms.;
2016-05-26 23:43:56.5579;DEBUG;Rubberduck.Parsing.Symbols.TypeHierarchyPass;Type hierarchies built in 34ms.;
A first chance exception of type 'Microsoft.CSharp.RuntimeBinder.RuntimeBinderException' occurred in Microsoft.CSharp.dll
A first chance exception of type 'Microsoft.CSharp.RuntimeBinder.RuntimeBinderException' occurred in System.Core.dll
Ah, my mistake on parsing the FileName. BuildFileName is part of VBIDE. The only time, AFAIK that it won't mimic the FileName, is if you are using a VBE that can compile a dll (eg. Office 2000/XP Developer editions)
@Comintern the project Explorer TreeView nodes have an lParam, which I've determined to be 96 bytes in length. All of those bytes appear to be 4-byte unsigned longs. So 24 Unsigned longs in total. Of those, many are 0. 2 of them are flags (possibly bit masked) indicating the node type and node type parent. The rest appear to be pointers.
I also noticed that a scan of the Excel memory reveals hundreds of Compound Binary/OLE File headers (only some of which seem to fit the Spec)
But some of those headers will, I think, be for the stream, and I suspect that one of the 24 TreeView node pointers will point me to the right stream.
Pretty new to this hence taking it as challenge. I have a master sheet in which Column A have all the file names( complete file name with .xls extensions). I need to copy data of column b in this sheet and paste it in all the files in a particular folder in a particular tab. There can be multiple...
Quackers before I forget as I have a headache heading home now, do we know that cucumber is actually a testing software which gherkin is for behaviour driven testing framework. en.m.wikipedia.org/wiki/Cucumber_(software)
just because linq is used doesn't make something oo. There's a world of linq being used, but very little use within the outer implementations that are oo
@Mat'sMug That's really harsh statement when I type it.
Indenting is something that should be done by the indenter. the code module shouldn't be written to directly, but should have a decorator between the refactoring (and infact all refactorings) and the code module
@Gareth I agree, I'm just saying, from the user's perspective, extracting a method, waiting for the reparse, then indenting the extracted method, and parsing again, ...doesn't need to be painful if we can avoid it.
@Mat'sMug we should prefer the FileName if it is available. Next preference is for the "Name" property of a document component whose "parent" property is the application. (Eg Workbook name, but not a Worksheet name), and if all else fails, either null or BuildFileName.
> I'm trying to get Rubberduck to parse an empty project in MSProject *2003* (yes, it's old, but it's all I have, so if you get no repro, close this issue), although MSProject loads ProjectGlobal (Global.mpt) too, so there *are* components to parse.
On open, RD toolbar freezes on Parsing. Hitting refresh causes it o freeze on Pending. Hitting refresh again, and again, finally got me to Parse Error, but when inspecting the errors, there were none.
> Additionally, if you then change one of the existing modules and commit, it won't include the new module in the commit. The only way to do it (currently) is manually commit in the desktop client.
> The error seems to occur in the Inspecting state, as that is what I see briefly before the exception.
I just got repro of the `Parser Error` state and empty Error dialog:
The *next* refresh after that zombie Parser Error results in an almost instant `Ready` state, but the Inspections window is empty, and subsequent refreshes leave the state at `Ready` until I add a module and hit refresh again.
@Mat'sMug Hi yep already using 1.4.3.2343 loving it, probably the best thing so far has been mucking around with unit tests, as a design tool (what a misnomer, lol). Will wait for a more stable ver 2... stick with it :-D
> Times aren't essential in the Test Explorer, but they are perhaps more useful in the clipboard export... Implemented in Test Explorer's clipboard export in #1595
i created an automatic upload tool, working great (most of the time). As i want to improve the code i have several questions:
1)Is it possible to make the iexplorer progress some kind of smoother? I don't like it that people can see the "sendkeys" actions. Is there a possibilty running the progre...
@ThunderFrame - My best guess would be that the lParam is a TVITEM, although the byte count is off. MS.Vbe.Interop.Forms has interfaces for the UserForm controls. I doubt we need it as a reference unless we do something with the form designer.
@Comintern @ThunderFrame we iterate form controls on UserForms; this enables refactor/rename to work with controls, both in code and in the designer context menu
VBA Rubberducking
VBA Rubberducking