Eloy Duran
eloy.****@gmail*****
Sat Nov 11 21:32:51 JST 2006
Hi Jonathan,
> I've attached to this message a small patch that adds some test case
> stubs for the qtkit support. I haven't added this to the repository
> due to a test failure.
Nice! I was planning on adding some tests in the near future, so this
is very much appreciated.
And good catch of the regex string btw ;)
> I have a test that crashes (bus error) before getting to QuickTime:
>
> QTMovie.movie.setCurrentTime("1:2:3:5.7/1000".to_qttime)
>
> Should the above code work?
Okay, about the test failure.
It is my believe, that you can't actually call setCurrentTime etc.
when the movie object isn't associated with a MovieController.
So I don't think you can use these methods when running from
just a script or irb etc.
I'll send you directly a attachment with the xcode test project I used
while writing qtkit.rb, in the Controller.rb file almost at the end you'll find
your test code which works.
So maybe it's better to do something like:
def test_qtkit_qttime_passing
movie = QTMovie.alloc.initWithFile_error('/System/Library/Sounds/Submarine.aiff',
nil)
assert_equal QTTime.new(585,600), movie.duration
end
> I saw your message on rubycocoa-talk about (I think) a missing link
> to QTKit.framework. Strangely, I don't get any link errors on my
> build from trunk.
Yeah, I was wondering about that too.
When I build it from the trunk it also succeeds.
But I did remember getting this problem once
in the early stage of creating qtkit.rb
Adding the QTKit.framework to the xcode project
solved the problem. And apparently it also did for this guy
that suffered from the same thing.
But why it's required 'sometimes' I have no clue actually??
Cheers,
Eloy.