I'll check that after the release. Please use the developer list for patche=
=2D--------- Weitergeleitete Nachricht ----------
Subject: Patch-in-progress: new seeking options for Kaffeine
Date: Freitag, 18. M=C3=A4rz 2005 15:55
=46rom: Christopher Martin <christopher.martin@...>
I'm fairly new to Kaffeine, and to coding at all I must admit, but
nevertheless I've managed to put together a patch uses the arrow keys to
seek. Currently, the left/right arrow keys seek 10 seconds, and shift+arrow
key seeks 1 minute. I've attached the patches.
In addition to implementing these seek actions, I modified
KXineWidget::slotSeekToTime so that it correctly displays "Position:
h:mm:ss" when a seek has occurred (previously, if you did a Jump to
Position, it would display 0:00:00 no matter where you jumped to). I also
modified it so that a seek, while paused, would not unpause playback
(giving the user more control).
There are two problems with the patches, at the moment. While seeking within
audio works very well, I noticed that seeking within video is not very
precise - Kaffeine will often move forward or back several more seconds
than was specified, giving a very rough feel to seeking (or using "Jump
to..", or even the mouse wheel over the slider, etc.). Pehaps the way video
is internally structured makes exact seeking difficult, but can anything be
done, or is this a current limitation of Xine?
The other problem is with audio playback. If you pause, and hit an arrow
key, the seek works, but if you then hit one again, Kaffeine jumps to the
beginning. For instance, if you hit the right arrow twice, Kaffeine first
jumps 10 seconds forward (as it should), then jumps to 0:00:10, as if it
thinks you are at the start of the track. It's as if getPlaytime() doesn't
return the current position after the first time you seek. This doesn't
happen with video playback, or when playback is not paused.
Anyway, I'm hoping that you'll want to incorporate these patches into
Kaffeine (maybe after 0.6 if you want to finish that soon), though ideally
of course the above problems would be fixed first (I welcome help, tips,
more code, etc.).
Cheers, and thanks for making Kaffeine,