Yes, method 1 was set during debug, as this method makes problem.
You could misunderstaood me. Firstly I deleted entire content of log file before I started all action described in previous post as points. So I started with empty .txt. file. Then I turned on programs (notepad, then VLC) and then turned on XMBC (however I could simply enable it). I did it in order I could archive log to rar without cutting out the part where problem showed up in .txt file (just for readability).
No matter debug was enabled/disabled. Problem appears debug is on/off.
I tried before play with "Delay between simulated keys", but it didn't help (CPU priority too). After your request I tried it now again. There is still no change
In fact after I changed it from 1 to 60 I could control it somehow that it didn't happen, and then I found that if I press RMB and click LMB, and then release both at once or one after one in very short time all is okey, but if I hold RMB, press and release LMB and keep still RMB for longer than a second (in case "Delay between simulated keys" is set to 60) problem occurs. When delay is set to low, so 1 I can't do anything, problem occurs always. I think there shouldn't be limit of time I can keep pressed RMB, because if I keep it too long after pressing and releasing LMB a bug shows up. Just an info I didn't mention before. When I release LMB, then release RMB, an option window pops up. I mean any window what shows up when you normally click right button. Then when button keys are released (no matter I close this pop up window with ESC key or not) each time clicking left button whatever action I set to chord, it is triggered.
The only thing I can do is to send you my settings you asked for. Attached.
----------------------------------------------------------------------------------------------------------------------------
NOTE: it's not always a good idea to set "Delay between simulated keys" from 1 to 60 even if that helped for typing before entered text which has to be displayed in some apps using simulated key strokes. Just by luck I found now that if I type some text in simulated key stroked, for example: XMBC is a great tool. Then clicking a mouse button the text is bound to, this text is showing very slowly, I mean letter after letter, the more delay the more time passing between showing next letters of that sentence. If "Delay between simulated keys" is set to some low level or just 1 then "drawing" time every next letter is so fast that an eye can't catch it. In my opinion it should be changed, that single letters entered to simulated keys shouldn't be devided by any delay. There only should be delay between "commands" like {ctrl}c or {ctrl}v. You know deleay between {ctrl} and c or {ctrl} v, not between single letters/numbers/etc as if I work with some app. profile when "Delay between simulated keys" set to high level, even 60 is OKEY and then for some reason I want go to notepad to enter some text, I have to wait long time it will be typed. Or I will manually open XMBC settings and change "Delay between simulated keys" again to 1. Then after closing notepad I go to XMBC settings to change "Delay between simulated keys" back to for ex. 60 and so on. Maybe it would be best you add special "Delay between simulated keys" for each app. profile, or like I said before change behaviour for beeing displayed text only. If a text is not a command, but a row of letters, then there shouldn't be delay between single letters. Normally if I want a delay between letters in simulated key strokes I precede each by {waitms<N>}, it's a correct way, isn't it? ...now I found a solution how you could solve it. Computer doesn't know you really want single kayes to be pressed as single ones or as whole sentences. Sometimes, and probably the most often we want they were pressed as single characters, as in some programs pressing them may trigger some action, but as you see there's chance we want a whole sentence. So the solution would be if you add to simulated keys special command. If someone wants to put a text to be displayed in no time then he could do it by this command: {sen:XMBC is a great tool} instead of XMBC is a great tool, what in that second case it would typed all letters with a speed depended on "Delay between simulated keys". In the first case that would be always immediately, no metter of value (1-60) in "Delay between simulated keys". The above are my thoughts for separate topic.
----------------------------------------------------------------------------------------------------------------------------
Ps. I found that this "bug" is really irritating when I set something in default profile. That doesn't must be in simulated key strokes, but of course in chording mode (RMB and then LMB). For example I set "Open Web Browser". When I'm on desktop (problably not only) and I hold RMB, then press LMB, web browser opens. Like before when I set {alt}{f4} it opens browser each time I just click left button (of course right is released). The difference is that reopening XMBC doesn't help at all to rid of this activity. When something is set to Default XMBC probile then only one option is to restart computer! Very strange as XMBC should start off from ZERO, but it just continue remembered operation from before quitting it.
And quite important information is (I mentioned it 2 weeks ago too if you missed it) that this behaviour occurs in choriding mode but only when second key is LMB, no metter what first one is. If that was LMB, but second middle or right etc, then all is fine.
off topic: that link to update to 2.15.3 doesn't work as well as when I check for updates directly from XMBC
You do not have the required permissions to view the files attached to this post.