Reply to thread

Message

<blockquote data-quote="morpheus_xx" data-source="post: 258250" data-attributes="member: 48495">Hi,I made some modifications to the TT api.Mainly I changed:- if CI open failed (no interface present), I don't reset the devicetype to unknown (there are other functions depending on devicetype and not belonging to ci)- I placed the retry loop back into Descramble (needed for me in first time init), but I notice if it once did timeout. If so I don't try again.- For users without CI the loop doesn't show an effect (I leave the function before)- not sure for this: in isCamReady I added the ciStatus (if there is &quot;no ca resource available&quot;, I set isReady=false)- Added base for the CI menu functions (not used yet)- There are some more messages shown in debug log, I'll reduce them when it's confirmed to be workingAs I can't commit to svn, could someone do it?GreetingsMorpheus_xx</blockquote>

[QUOTE="morpheus_xx, post: 258250, member: 48495"] Hi, I made some modifications to the TT api. Mainly I changed: - if CI open failed (no interface present), I don't reset the devicetype to unknown (there are other functions depending on devicetype and not belonging to ci) - I placed the retry loop back into Descramble (needed for me in first time init), but I notice if it once did timeout. If so I don't try again. - For users without CI the loop doesn't show an effect (I leave the function before) - not sure for this: in isCamReady I added the ciStatus (if there is "no ca resource available", I set isReady=false) - Added base for the CI menu functions (not used yet) - There are some more messages shown in debug log, I'll reduce them when it's confirmed to be working As I can't commit to svn, could someone do it? Greetings Morpheus_xx [/QUOTE]

Verification