



Code: Select all
{PRESS}abc{WAITMS100}{RELEASE}cba
Code: Select all
{press:abc} {release}
Code: Select all
{CTRL:{ALT:b}}
LOL - that will teach me to say things like "its quiet in here"!!!BriHecato wrote:1. You could add a little graphic - image of the desktop (or windows window) behind the 4 checkboxes (profile quadrants) make it slightly bigger - that suggest new users what is this about (and maybe baloon tooltip "you can define quarter of window works with this profile").
made in paint
2. Simkeys window could be rsizible vertically (not just scrollable help content).
3. Example:results in "abcba"Code: Select all
{PRESS}abc{WAITMS100}{RELEASE}cba
so {PRESS} or {RELEASE} still work only for one next character not for the group of keys.
4. In simkeys since we have {wait:...}, {run:...}, {hold:...} and {madd:...}, maybe change syntax of {press} & {release} towhere releasing all by default (i don't know how it could be used by anyoneCode: Select all
{press:abc} {release}
)
Next there could beglobal syntax style if you know what i mean.Code: Select all
{CTRL:{ALT:b}}
5. Maybe idea for next version, buttons in simkey window to one-clik-add-function (OCAF):
6. So far no bugs at all - only vivaldi and his strange behaviour. I've noticd that profile doesnt work if it's connected to vivaldi.exe. I need to "specify window" for it to work. And even then when i have only 1 tab open chordings doesn't works (my 4th -> right "{ctrl}p" chording). It is like that since i've switched from Firefox to V. It's definately not XMBC issue.
Yes, you are rightphil wrote:Well, being quiet clearly does not mean no bugs, just not enough testing....
Does not seem to happen here but I'll try and reproduce and fix.maxoku wrote:Sub-regions works great. But everytime I want to edit a specific window (not sub-region windows) that option is automatically checking on with some random values for bottom and right.
As it should - because you are editing the middle button, so that action is what happens if you just press/release the middle button, without performing a chorded action.maxoku wrote:In the window for button chording instead od middle button is written Default (no chord).
Number spin controls should not respond to scroll when they are disabled - but they are - so thats odd - will take a look.maxoku wrote:When I scroll on disabled options (for me) tilt wheel I get an '#invalid item'. When I do it in chording window I can practically set any option and click on the button to set simulated keys. I suggest to disable also scrolling over disabled options or something to block it.
Odd - not doing that here, but Ive had so many problems with the drawing of those buttons - it could be related (be glad its there at all!). Probably not going to touch that as I cant reproduce and I don't want to make it worse again!maxoku wrote:When I click on the button to set simulated keys it visually stays pressed. I mean the background of the button isn't refreshed immediately. I can e.g. cover it with another window for a moment and it's refreshed. Icon itself returns to previous position and I can click it again (also visually). And the whole button after pressing looks like it has been doubled or something, unless I cover it with simulated keys window and after closing it the button is pressed, but not doubled lol. I use classic style, so maybe only I have that problem.
That's windows doing that - nothing i can do about it as far as I know (without an awful lot of work) short of adding an extra space maybe before itmaxoku wrote:In settings Updates & Logging when it's written 'Leave blank...' I don't see the first letter, so it might be good idea to set a left margin or something for that. But maybe only I have that problem on classic style. Nevertheless I did something in my translation fix to overcome this problem lol.
Must be an XP issue - it's not happening here on windows 7 or 10. Quite frankly, Ive been seriously thinking about dropping XP support for some time now. I probably wont do so, but Im not going to be making any special efforts to fix XP only problems. If/When I upgrade XMBC to Visual Studio 2017, I will have to drop XP support as I don't believe the 2017 C++ runtime supports XP at all!maxoku wrote:And don't forget about my topic about task bar problem.