[Kde-bindings] [bindings] [Bug 330800] New: Custom signals not working with ruby 2.0.0

[nicolas.salguero at laposte.net]

https://bugs.kde.org/show_bug.cgi?id=330800

            Bug ID: 330800
           Summary: Custom signals not working with ruby 2.0.0
    Classification: Unclassified
           Product: bindings
           Version: 4.11.4
          Platform: Mageia RPMs
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: kde-bindings at kde.org
          Reporter: nicolas.salguero at laposte.net

Hi,

With ruby 2.0.0 and qt4-ruby 4.11.4, a program can use predefined signals but
custom signals are silently ignored.

When searching the words "qt4 ruby 2.0.0 custom signal" on the Web, I found
this page http://stackoverflow.com/questions/15583114/qtruby-emit-does-not-work
where someone says qtbindings 4.8.5.2 is not affected and, by comparing between
qtbindings 4.8.5.2 and qt4-ruby 4.11.4, I found the main difference is usage of
"rb_frame_this_func()" instead of "rb_frame_callee()".

So I tried to recompile qt4-ruby 4.11.4 with the attached patch and the custom
signals work again (I have successfully tested with a game I wrote :
http://onetofive.sourceforge.net).

Hope this helps.

Nico.

Reproducible: Always

Steps to Reproduce:
1. Launch a program that use ruby 2.0.0 and qt4 binding.
Actual Results:  
Predefined signals work but own defined signals are silently ignored.

Expected Results:  
All signals work.

-- 
You are receiving this mail because:
You are the assignee for the bug.