|
Slink-e / CDJ Discussion Archive #1 Re: Trouble with new SlinkX and CDJ in 95Posted By: Colby Boles <cboles@s...> In Response To: Re: Trouble with new SlinkX and CDJ in 95 (Jon Welfringer)
The reason is that new methods and properties have been added to the SlinkX control. You will need to rewrap/recompile your app to get it to work with the new version. These are just growing pains - hopefully this won't happen very often. If you check the site tommorrow you'll be pleased to find documentation for it too as part of a new HTMLHelp based help system I'm putting in place for both your local install and the website. Converting the lowlevel timings to the .cde format is a tricky process. If your curious how it works, start with CDev::RLCToBin() in the Dev.cpp Slink-e class file. As I've described before, you can get the SlinkX control to do most of the work for you if you know the timing characteristics (e.g. like those in a include file like SONYIR.CDE) of the waveform you want to decode. If you load a device with just the timing info, you will get a "nomatch" events which tell you what the bit patterns are. I'll get on this soon enough and make E-Z learn generate the full-fledged IR .cde files for you. Colby
Slink-e / CDJ Discussion Archive #1 is maintained by slinke-bbs-owner@nirvis.com with WebBBS 3.21. |