Bug report: Assigning different blocks to the click events of separate buttons

Hello list,

I was playing around with the code Scott Guthrie put up back in July
about calling WPF from ironruby
(ScottGu's Blog - First Look at IronRuby)
and I came across the following issue:

I took the sample code and added another button with another ruby
block for the click event just below the one labeled “Push Me”. This
second block never gets executed when I click the second button, but
rather the first block gets executed. Is this a known issue, and if
so, what is causing the problem?

Thanks

Terence

On Jan 4, 2008 6:52 AM, Terence L. [email protected] wrote:

I took the sample code and added another button with another ruby
block for the click event just below the one labeled “Push Me”. This
second block never gets executed when I click the second button, but
rather the first block gets executed. Is this a known issue, and if
so, what is causing the problem?

It’s a known issue. At the time it was previously identified, John L.
wrote:

“We’re trying to track down the cause of this, but we know that we’re
not building the correct rules for all cases in our ActionBinder.
It’s likely related to this, but we’re not sure right now.”


Curt H.
[email protected]