[Pending] Proper handling of Extended event descriptor (1 Viewer)

quba54

Portal Member
November 24, 2007
17
0
Warsaw
Poland Poland
Problems:
- if more than one “extended event descriptor” is sent to specific event and text begins with control codes with character table the EPGLanguage.text field contains badly concatenated string. There is no problem when there is only one descriptor for event. But when there is more descriptors each next descriptor text is added with control charactes to EPGLanguage.text field.
- You don’t process item description field (you just skip it). In polish EPG there is info about actors, year etc.
 

Attachments

riksmith

Portal Pro
April 18, 2009
1,856
322
Netherlands Netherlands
The item list should not be added to lang.event, if i read correctly this is the name of the event. It think it needs its own field if we are going to implement this.
 

chemelli

Retired Team Member
  • Premium Supporter
  • September 28, 2006
    6,159
    2,264
    46
    Milano, Italy
    Italy Italy
    Country flag
    quba54, can you provide an updated version based on current trunk and riksmith's comment please ?

    Simone
     

    jaobr

    Portal Member
    November 6, 2006
    22
    5
    Found a bug in the extended event descriptor decoding (tswriter epgdecoder.cpp).

    When an EPGLanguage is created the extendedEventComplete property is not initialize (should be set to false).
    This leads to that extended event descriptor decoding somtimes works and somtimes the text is skipped.
     

    Users Who Are Viewing This Thread (Users: 0, Guests: 1)

    Top Bottom