Sweden
Unfortunately I can't agree with wimpies, I tried rev12268 and there are still some problems. In most menus it works but in some I still experience double-clicks. For instance in the context menus (F9-menus) and sometimes while I browse my music and press "enter" on the remote.
X10-remote - experiencing "double-clicks" (1 Viewer)
- Thread starter Spragleknas
- Start date
Hey guys,
I have some bad news. I rewrote it from scratch (in a more reasonable way) so I could make sure I was doing everything correctly, and the problem is still there. I'm going to give this another couple of hours of my time, but it doesn't look promising. This might be the best it gets.
~Steve
I have some bad news. I rewrote it from scratch (in a more reasonable way) so I could make sure I was doing everything correctly, and the problem is still there. I'm going to give this another couple of hours of my time, but it doesn't look promising. This might be the best it gets.
~Steve
OK, I've got it fixed, but it require me to make some very large changes that are reverberating through mp. It might be awhile before this makes it to svn. and by fixed, I mean this isn't a hack.
Its kind of complicated to describe not knowing your background, but here goes.
In C++ you allocate all of the memory yourself. This is convenient from several perspectives, but difficult to manage. In C#, you give up the freedom of memory allocation for the benefit of not having to worry about it. The remote code uses COM interfaces which depend on being released reliably. It was very difficult to do this, and even when I did it correctly one would still get double key presses before everything was truly released. So, the key is not releasing it in the first place when we go to suspend. Less work leads to better results.
In C++ you allocate all of the memory yourself. This is convenient from several perspectives, but difficult to manage. In C#, you give up the freedom of memory allocation for the benefit of not having to worry about it. The remote code uses COM interfaces which depend on being released reliably. It was very difficult to do this, and even when I did it correctly one would still get double key presses before everything was truly released. So, the key is not releasing it in the first place when we go to suspend. Less work leads to better results.
