Hi
Last week I put up a new version of the LIRC interface to
http://mypage.bluewin.ch/tarnold/rosegarden/lirc/
(050710.rg-lirc.patch and 050625.lircrc)
For an eventuel release, we should find some place to put 050625.lircrc
such that users will find it when looking for LIRC support (e.g. xmms-lirc
puts its example ~/lircrc into the top level source directory and debian
installs it into /usr/share/doc/xmms-lirc/examples/lircrc while gentoo puts
it to /usr/share/doc/xmms-lirc-1.4/lircrc.gz).
Currently, I have problems testing it, since the current sequencer does not
let me record no more (CVS 1.0 works fine). It does not
matter whether I configure with nolirc=1 or not, so I hope it's some
temporary problem.
The 050710.rg-lirc.patch changes only lirccommander. The main change is that
it now consequently uses qt's signal/slot mechanism and that it "... does
some breakneck object navigation to reach the selected track LED's."- which
reads
// local rg object navigation
Rosegarden::TrackId getSelectedTrack() const
{ return
m_rgGUIApp->getDocument()->getComposition().getSelectedTrack(); }
int getSelectedTrackPosition() const
{ return
m_rgGUIApp->getDocument()->getComposition().getTrackById(getSelectedTrack())->getPosition();
}
It reconnects the TrackButtons on each
RosegardenGUIApp: SIGNAL(documentChanged(RosegardenGUIDoc*)
I found this patterns by grepping through the source code. Is this way how it
should be or should it be changed somehow?
Regards
Toni
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Rosegarden-devel mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
