Hi!
I just made a simple OS X dashboard remote control widget for Frodo that uses JSON-RPC over the WebSocket (http://forum.xbmc.org/showthread.php?tid=19448&page=3). In general everything works great, but I noticed that when using the remote for extended periods, it often leads to a crash of the Remote Communication Server. This typically happens when the widget either opens or closes the virtual keyboard.
To detect the opening and closing of the keyboard, I use the OnInputRequested and OnInputFinished notifications. When looking deeper into the issue, I noticed that every time the virtual keyboard is either opened or closed, the widget receives an additional OnInputRequested or OnInputFinished message. So when opening the keyboard the first time, I receive one OnInputRequested message. Next, putting in text and closing the keyboard yields TWO OnInputFinished messages. Opening the keyboard again, then yields THREE OnInputRequested messages, and so on. I don't see this behavior with other notifications.
I'm not entirely sure that this has to do with the crashes I observed, but it seemed to me that this is an unwanted kind of behavior?
Cheers!
I just made a simple OS X dashboard remote control widget for Frodo that uses JSON-RPC over the WebSocket (http://forum.xbmc.org/showthread.php?tid=19448&page=3). In general everything works great, but I noticed that when using the remote for extended periods, it often leads to a crash of the Remote Communication Server. This typically happens when the widget either opens or closes the virtual keyboard.
To detect the opening and closing of the keyboard, I use the OnInputRequested and OnInputFinished notifications. When looking deeper into the issue, I noticed that every time the virtual keyboard is either opened or closed, the widget receives an additional OnInputRequested or OnInputFinished message. So when opening the keyboard the first time, I receive one OnInputRequested message. Next, putting in text and closing the keyboard yields TWO OnInputFinished messages. Opening the keyboard again, then yields THREE OnInputRequested messages, and so on. I don't see this behavior with other notifications.
I'm not entirely sure that this has to do with the crashes I observed, but it seemed to me that this is an unwanted kind of behavior?
Cheers!