Re: VX8300 Calendar Bug

Simon, Joe:

I think I understand the ringer assignment better regarding the VX8300 
calendar packets.  The builtin ringers are assigned by number, 0 through 
15.  However, any additional ringers are assigned an index of 100 (hex 
64).  Now the kicker:  The additional 256 characters that until now have 
been unknown in the event packet, are in fact, the LOCATION of the 
ringer file!!!! 

I have a lot more to do, and will have many questions for both of you!  
;-)  I have updated several files locally, and will submit them to you 
within a few days, once I think I have things finalized.  So far, I have 
updated the following files:
    p_lgx8300.p  --  Updated the protocol for the calendar event
    com_lg.py  -- Updating the "class LGUncountedIndexedMedia" methods
    com_lgvx8100.py  --  Continuing the updates for the VX8300
   
One thing I still cannot fathom is how the list within the GUI, 
specifically the calendar ringer tab, is generated.  I have fixed the 
"results" variable within the LGUncountedIndexedMedia class (i.e., 
"getringtones" method) but it does not appear the GUI uses it; instead, 
it looks like it hard codes the class to pull the getringtones method 
from (i.e., self.commphone.getringtones).   :-(      Joe, could you give 
me some help here?

Thanks again for all of your help!

Michael C.



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV