Yep, still looks like an issue. Tomas, the bug Michael refers to is a RubyForge
bug you opened in January:
http://rubyforge.org/tracker/index.php?func=detail&aid=23494&group_id=4359&atid=16798
So I created a CodePlex bug for it:
http://ironruby.codeplex.com/WorkItem/View.aspx?WorkItemId=1594
In the future, if there is a RubyForge bug that anyone cares about, please move
it over to CodePlex.
~js
> -----Original Message-----
> From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-
> bounces at rubyforge.org] On Behalf Of Michael Delaney
> Sent: Friday, June 12, 2009 8:22 AM
> To: ironruby-core at rubyforge.org
> Subject: [Ironruby-core] Calling Explicit Interfaces
>
> Hi,
>
> Is this still a bug i.e. bug #23494.
>
> i''m trying to use cucumber test a WPF app using the WPFAutomation.
>
> there''s an explicit interface implementation of
> System.Windows.Automation.Provider.IInvokeProvider on the
> ButtonAutomationPeer class.
>
> at the moment i''m getting around it by creating a helper object in
c#
>
> namespace UIAutomation {
> public class InvokeHelper {
> private readonly IInvokeProvider _provider;
> public InvokeHelper(IInvokeProvider provider) {
> _provider = provider;
> }
> public void Invoke(){
> _provider.Invoke();
> }
> }
> }
>
> and then call in IR:
> ih = InvokeHelper.new bp
> ih.invoke
>
>
> Is there another way to do this??
> Regads.
> --
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> Ironruby-core mailing list
> Ironruby-core at rubyforge.org
> http://rubyforge.org/mailman/listinfo/ironruby-core