Buttons To Press 6
Modification by Ronald Rael Harvest, six@thevillage.dhs.org

This is a modification of BTP 1 intended to emulate the behavior of
"irremote," with the exception that it only allows you to define one remote
control view.  In case anyone's unclear on why that would be nifty, it's
because it lets you define remotes with buttons that have different 
arrangements and shapes and not just square dots in rows like BTP 1 does.

The configuration file format is fully compatible with single-view config
files from irremote.  If you're creating a new remote.ini file though,
you should be aware that this program ignores "remote=" directives and that
anything that starts with "button" counts as a button definition and if you
put numbers between the word "button" and the equal sign (like in irremote)
those numbers are ignored.  Included is the remote.ini file I'm using for
my remote, as well as my lircd.conf so you can see my remote definitions.

Up to 100 buttons may be defined (like in irremote) but only 1 remote view.

I've removed the image buttons code as irremote didn't have similar 
functionality.

Also I made a Makefile.  The Makefile assumes that the cross-compiler is 
in your path and that your development libraries are in 
/opt/snow-gcc/lib/snow.  If this isn't true, you'll need to edit the
Makefile, which shouldn't be too confusing.

BTP 1.0 is by Martin "Sam" Samuelsson, sam@home.se.  It's quite possible
that I've reworked significant portions of his code, but I still feel this
should just be termed a "modification" because I have very low self esteem.

[Some last minute comments from Ronald]

If you generate your lircd.conf with irrecord on a lirc-equipped PC
(which I did) you may have to add "frequency" lines into the resulting
config files in order to get them to work well, which it turned out I
needed for two of my four remotes.  This is because irrecord doesn't
return the actual carrier frequency of the signals it detects, so the
config files default to a carrier of 37000 but actual popular remotes
apparently vary from 34000 to 44000 (according to the lirc manual
page, anyway, which is where I read about this)...  So what I ended up
doing for mine is just starting out with a "frequency 34000" in there
and then incrementing by 500 until I got one that worked.

[EOC]

What follows is selected parts of the README file included with BTP 1.0:
---------------------------------------------------------------------------

BTP is an embracement of rc, and meant to be used on Agenda VR3. It begun its
life as an experiment with FLTK, and has evolved into a pretty usable thing.
The worst thing about it is the fingerprints on the Agenda display.

This application still lack a couple of things:
 It doesn't do that nifty autorescaling seen in most Agenda apps, probably
because I ignore Flek most of the time.
 It doesn't start lircd. You'll have to find the best lircd config file for
your equipment and feed it to lircd before trying btp out. And be sure
you're root, or you won't be allowed to do anything.
 The error messages aren't very helpful. In general, if btp fail for
some reason or another: Make sure lircd is running.

Documentation about lircd and how to build config files for it can be
found at the project's web site: http://www.lirc.org/

I hope btp will be of use to you!

/Sam
