avprosjekt
That's right.
toggle quoted message
Show quoted text
There is no comunication/fb from the OSD menu state and back to the API we have access to, and we can only use the IR emulation codes to control the OSD hierarchy menu. Their philosophy has always been that when you control the video system with a 3'rd party control system you don't need OSD and have even recommended to disable it... (OSD is for IR remote) I can follow that to the extent that the users focus, during maneuvering through addressbooks and estabishing a call (which is among the the most challenging tasks), should be on one place, i.e focus on either on the Touch Panel or on the screen (OSD), and not both. But after complains from partners and clients they once again have realized that a combo, with some OSD warnings and some info may be the best way.(read as it is on the MXP). In TC4.xx and TC5.xx Cisco have experimented with different OSD combos that do not work as well, but from TC6.0(which is to be released this autumn) I have been told that an enhanced combo with several selected OSD variables from API is included. We will see..... It is always a matter of taste but my preferences and experiences goes towards a none OSD version except for reading Far End statuses and callstat's, but it is dependent of a module that works flawlessly, and that is a whole different discussion.. :-) -Stig --- In Crestron@..., "Chip" <cfm@...> wrote:
|