@IvenBach - You don't waste our time. OP on that question did, with about 7 people who where repeatedly asking what the question was until one of them guessed.
Or is knowing that a declaration has a type of DeclarationType.Control enough to know that that declaration also implements all of the members of Control/IControl, while other declarations only implement some?
@Comintern Extend the visible and hidden Icontrol members to DeclarationType.Control declarations, and only extend the visible IControl members to declarations having a Type that is an implementation of IControl?
I just don't know how to extend members the other way (without doing code-path analysis). For example, a variable of type Control can invoke members of the underlying type:
Dim ctl As Control
Set ctl = Me.Controls("ListBox1")
Debug.Print ctl.ListCount
The extended members don't appear in Intellisense, but they do compile. When stepping the code, the Locals window shows the extended properties and their values.
hmm - 4G delays - I may be confusing things for you.... A variable named `myListbox`of Type `ListBox1` that is set to `Me.Listbox1`, can have an invocation of hidden `Control` member `[_SetHeight]` and it will compile, but it won't run. It can have invocations of visible `Control` members such as `Height` which won't appear in Intellisense, but will compile and run. But a variable named `myControl` of Type `Control` that is set to `Me.ListBox1`, can have invocations of both visible and hidden `Control` member such as `Height` and `[_SetHeight]` (that both *do* appear in Intellisense), **and…
@PeterMTaylor Meh, I gave up on that a while ago. If there's an answer in what he wrote, maybe somebody else can figure it out. TBH, the question itself should have been closed about 9 hours ago for about 3 different reasons.
I met Charles when he was in Melbourne last year. Told him about Rubberuck and has asked if it was written in C++ (with which he is most familiar). When the anwswer was no, he seemed disapproving.
In .NET? A bunch of ways. Declare as object and reflect on the COM assemblies or use dynamics. Declare IUnknown and IDispatch and go old-school on it. Drop to unsafe mode and work with the vtables directly. Etc. Am I understanding correctly that by "cannot obfuscate object model calls" you mean that a .NET coder would have to actually type "Excel.Application.Calculate" into the code somewhere? — Comintern17 secs ago
Thank you @Mat'sMug @Comintern @ThunderFrame, more and more of what interfaces are and how to use them is clicking. I was working on one today. Your earlier patient explanations helped me so much to grasp the concept and start work.
I am currently trying to fix the TypeBindingContext and I am a little bit astonished about a test I broke. Is it really legal to have Public WithEvents anything As BindingTarget where BindingTarget is a standard module?
when I make a completely empty workbook, add a RD test module with early binding, the error occurs. it's the same error given with real application. at that time the only referenced libraries are whatever VBA adds automatically and RD
when I make a completely empty workbook, add a RD test module with early binding, the error occurs. it's the same error given with real application. at that time the only referenced libraries are whatever VBA adds automatically and RD
After finding this strange test, I just had another look at the EnclosingProjectComedBefore... tests that failed randomly. They all test how the resolver behaves in cases where the code does not compile.
Seems there's an unfortunate confusion here. The Rubberduck project I maintain is a COM add-in for the Visual Basic Editor (VBE), the IDE people use to write VBA code... as you may have noticed on the website you got this email address from.
On Mar 21, 2017 16:40, "Dannae Gomez" <dannae.gomez@getapp.com> wrote: Forgot to include the link to the article you were featured in! My apologies! https://www.getapp.com/blog/6-slack-apps-for-small-business/
Oops that was the draft reply.. there's more to it
But whatever.. That duck is nowhere in my google search results. Best of luck...
Hm another test thinks that Public WithEvents anything As BindingTargetName should resolve to an Enum, which technically is correct, but leads to a compiler error.
VBA Rubberducking
VBA Rubberducking