Page 1 of 1

Conditional statement request

Posted: Mon Sep 30, 2019 4:41 pm
by Kukurykus
1) Please add to simkeys IF command that would be used only for 3 Windows keys: CapsLock, NumLock and ScrollLock. They all are either enabled or disabled (what often can be displayed on keyboard). If you do something like if(CL) or if(NL) or else if(SL) we could have conditional statements. I know once you said conditions would be hard to implement, but in this case I think that's very easy. For example:

{if(SL):wait(1){ctrl}v}




2) You could do it also for clipboard, so either it's empty or filled:

{if(CB):wait(1){ctrl}v}

btw it could be great to have clipboard content could be pasted or read:

{if(CB):wait(1){CBP}}

{if(CB=='abc'):wait(1){CBP}}




3) internal XMBC environment variables (overall or app/process specific):

{env:'var','abc'}

{if({env:'var'}):{ctrl}v}

It could be cleared by {env:'var', ''}

{if({env:'var'=='abc'}):{ctrl}v}




If you do the 1st item, then it's okey for now. When you have time 2nd is good too, later maybe 3rd? :D

Re: Conditional statement request

Posted: Mon Sep 30, 2019 8:43 pm
by phil
Sorry no chance. The simkey is already too complex. I'm not about to implement a custom language parser, syntax checker and all that guf, never mind then having to run it too! If you want to do this, build an autohoteky script or any other complied script and call it from XMBC.

Re: Conditional statement request

Posted: Mon Sep 30, 2019 8:52 pm
by Kukurykus
I use already Autohotkey script I wrote myself that is triggered by XMBC (thx. to .exe), and as I remember it has only 2 short lines. Maybe in Autohotkey it's easy, but not in language you use together with XMBC, but checking just status of those 3 buttons from first point maybe won't be so complex. Also hard to understand by users. else / else if wouldn't be needed. But okey, maybe in some future then or at all.