That certeinly shouldn't go to almost finished BETA topic 
all things are new and not related to its content.I just went where I were mostly active 9 months ago, it's why there. I hope one new idea per one therad can be that we need, but there should be separate section on the forums where all related topic would be created. If after discussion you accepted some idea you could personally anounce it in Beta topic, where people could talk about new thing added to XMBC for tests.
Item 5 (changing layers):
yes it already waits years to be placed between other simulated strokes insructions
Item 6 (code examples):
you are right. I go read more from topics on this forum and microsoft documentaion. I was just more interested not how to use it, but adventages it gives, I mean how it can be used by other peoples, what they do with this stuff, because I have no ideas what I could do with it now.
Item 4, 9 ({CRT} for creating folders and text files & {CB} for clipboard):
the easiest to implement, and personaly if I had that clipboard command I could forget all other items I came with
at least for some time ha ha However now I have even more advanced option for some non existing future That would work with "conditional". So if there were "variables" section we could put somethig like this in simulated keystrokes blank:{cp == 'someText' ? 'someVar1' : 'someVar2'}
where 'someText' would be content of clipboard put by user, or rather a program / script he wrote / used, before clicking some XMBC coded button. While someVar1 and someVar1 were stored in VARIABLES section of XMBC (the way I described it in previous post).
Of course it's more my fantasy and the only thing I do need for now is simple {cp:'someText'} and cp:''}
Item 6 (mouse speed):
it could be done together with "Change movement to scroll" proposed by Killy in this topic viewtopic.php?f=6&t=2743&p=14535#p14535 So we already had 'Mouse speed', 'Delay between simulated keystrokes' and 'Change movement to scroll' (whatever it is) in general settings as well as for certain app.
Item 2 and 3 (paths and variables):
Well, if there won't be nothing interesting to do at the moment maybe one day it can be implemented
In the worst case you can add it as another bookmarks (separate for variables and paths) after Layers, Scrolling, Options, or to General Settings a way it's now done for Hotkeys and Modifier Keys.Item 1 and 8 ('Button Held Time Dependent Action' as part of default (no chord) 'Button Chording' and {stp} command)
I think the first item would be some bigger work surely to do it, but nothing impossible and making conflict (when I try to imagine it). BHTDA is quite new, but I feel like there is a lack of it combained with BC as it seems to me be very intuitive that default button should be extended of it.
{stp} is hard probably to do too, maybe harder than I think or undoable the way I described, however I tried everything from XMBC to let live 'method 8' in my work. Unfortunately when my work is dynamic I can't use it without thinking all the time can I already move my hand that it doesn't spoil planned action.
Thx for reading again, and good lack with releasing new version of XMBC extended of current BETA!
. When I enter the Change Movement to Scroll mode the mouse wheel doesn't work at all. I think that it should work as normal scrolling or just work like every other mouse button to exit the mode. Probably it happened in a one of previous betas where you gave to every mouse button function to leave the mode.
) 
