Hi Coley ,
apologies for the abrupt & prolonged abscense,......Who's been a busy boy then ?
I have set up my Dusky as follows
child of GenericPC as core/hybrid
Category #71 Interfaces
manuf Heenan #1153
#37 ComportOn PC string
#76 COM Port parity/bit/stop string N81
#78 Baud rate strinng B5700
#48 Number of Ports int number of outputs on dusky 2
#81 Channel int 1
#171 Port int 2
I think more (int) parameters need to be added to account for the number of Dusky's on the system and to specify which one the template will refer to
I also think the driver should be able to address both usb & rs232 variants
I set the sky box up as ............. a child to the dusky....... sattelite>AV........ir controlled
..........this is what DCEGen used to spit out the code... which as yet hasn't been compiled and tested ...I'm trying to work out what it does atm
so I've nothing to merge as yet.
So that we (and anyone else in future) are singing off the same hymn sheet , can I suggest :
a) we agree & submit the required temlpates to "fix" the template numbers & device data numbers?
for e.g sat box ...manufacturer Sky ..av/Sat box.....name== "duskySky+/hd"
and another "=duskySky" for the standard digibox
b) open a wiki page (I can do that ) to document what we're doing, which will also give us a method to swap code and an easy entry point for anyone to jump in , as well as a standard working base ?
EDIT: (As my understanding of programming is VERY limited ) ...I'll get to work on the templates and
the wiki (edit draft page at http://wiki.linuxmce.org/index.php/Dusky_Sky_Controller..Driver_Effort
& try to follow what you're doing, chipping in where I can.
PLEASE can anyone recommend a beginners guide to OOP and to C++ ?