That is pascal it will not work. It was just a real example of the code logic itself.
the pseudo code is using the actual functions to check and call them. i is for the mouse click and the Control_R is also from the documentation for what you said you are using. you being the user of same said software would be the one who'd have a better chance of figuring this out.
Quote:
Originally Posted by dancer_69
From psudo code I can understand that it's a way to keep track of mouse button if is clicked or not.
|
You seem to grasp the logic at lest in its minimum form. You can see what it is doing and obtained an almost correct conclusion. It is a means to check the state of not the mouse button itself but what it is controlling. The click fires an action. That action fires another action. Depending on the sate of the thing needing to be acted on. If not on then off. If on then off. regardless which time you clicked the button. It is kind of like a three way light switch.
Where one switch can turn it on or off, and the other switch can do the same.
If the light is on, and you flip the other switch it will turn it off, because it was already on. If you flip the other switch it will do the opposite. Does not matter if the switch is up or down. The action is flipping the switch, the state is if the light bulb is on or off to start with.
the result is if on then off, if off then on.
the process is if the light switch is flipped(clicked), and if light on then turn it off, if light is off then turn it on.
The state of the mouse button is down, or up same as the right and left mouse buttons, where you can check each state of the button as well, and act on it separately. then it checks the state of the thing being acted on. the same process goes forth.
State-> action Boolean logic. (yes or no, 0 or 1 no shades of gray.)
Quote:
If mouse clicked is true then set Control_button state clicked true if the Control_button state is already true, then it sets it false instead.
|
Now you just need to build up your knowledge base from that. Here are a bunch of links to help you.
https://mike42.me/blog/2014-11-07_us..._your_workflow
https://blog.sleeplessbeastie.eu/201...-and-keyboard/
http://www.linuxjournal.com/article/10808
https://anton.logvinenko.name/en/blo...eystrokes.html
http://askubuntu.com/questions/49992...with-xbindkeys
http://askubuntu.com/questions/10392...eypress-in-xte
https://liquidat.wordpress.com/2013/...dkeys-and-xte/
A little experimentation on your part is going to be required. That should be plenty to keep you going.
keywords 'xte linux examples'