Eloy Duran
eloy.****@gmail*****
Mon Jun 2 19:48:36 JST 2008
Hi all,
This is more so I don't forget, but this is a bug I just posted to
radar (#5978609).
Like the notes say, I still need to try a workaround.
Also I should note that pinpointing the problem was thanks to Patrick
Geiller.
Cheers,
Eloy
=
=
=
=
=
=
=
=
=
========================================================================
Summary: A NSView subclass completely defined in RubyCocoa does not
have a funtioning CA animator proxy.
Steps to Reproduce: Define a NSView subclass completely from ruby and
try to use the animator.
Eg: @myCustomView.animator.frame = OSX::NSRect.new(0, 0, 100, 100)
Expected Results: I'd expect it to animate from the current rect to
the new one specified.
Actual Results: It moves to the new rect immediately.
Regression: Not known.
Notes: One workaround, which I haven't tried yet but would probably
work, is to define the NSView subclass in Objective-C and then open
the class from ruby and define it's methods etc.
Extra: This is what #animator for a NSView subclass defined in objc
looks like: <_NSViewAnimator_NSScrollView: 0x5a4ec0> Animator Proxy
for: { <NSScrollView: 0x56b7e0> }
And this is what it looks like for a completely RubyCocoa defined
NSView subclass:
<LayerView: 0x575a60>