![]() ![]() After the Script Separator, we see a value of 101, meaning that this command will be executed 1 millisecond after the command in line 1. As expected, a Script Separator follows immediately after the 6 because there is no longer a location where a click is being active, meaning that we no longer need coordinates. I'm not sure as to what the next value of 6 in lines 2 and 3 actually means, but I think of it as a spacer, and I do not think that it is needed, as this version of the script works as well and performs the exact same function. The 0 that follows tells us that a click has not been initiated/is not active. ![]() We see a format very similar to line 1 up until we get to the values after "MULTI". The value of 100 following the Script Separator tells us that this command will be executed 100ms from when we press the play button in our Nox's Macro Recorder window. The Script Separator that follows indicates that the bulk of this line is done. The next value shows us that the click is taking place at a location of X: 66, Y: 275. The next value is a 0, so we know that it is just a click and not something like a drag. The value next to "MULTI" is a 1, so we have initiated a click. In the first line we can see that we are doing something with the mouse as shown by the "MULTI". The Script Separator in each line separates the 0 from the resolution. Now that we have an understanding as to what is happening here, let's try to analyze the entire script.Įvery line begins with a 0, so we know that we wont have to worry about keyboard inputs (we would have a 1 instead of a 0). ![]() This is a timestamp which indicates when the command is executed in what I presume to be milliseconds. Using the first image as an example, we know that my Nox resolution is 240x420, so the click will occur at the location X: 66, Y: 275. This rectangle holds the location of an input given in terms of X, Y as determined by your resolution. I believe that a value of 0 would mean no modifier, and a value of 1 would initiate a mouse button release.īy now you will have noticed the Yellow rectangle following the Pink one in both images. From what I've seen, this "column" will most often be occupied by a 0, 1 or 2. Here is what that would look like in a script. For example, if the value is set to 2, it would mean that the mouse is being dragged. I like to think of this value as a secondary function. To the right of the Purple rectangle is the Pink one. Notice that the lines beneath hold a value of 0 instead, showing that the mouse button is not being clicked. For example, you'll see that it holds a value of 1 in the first line, meaning that the mouse is in an active state or has been clicked. I believe this to be an action state of sorts. This is short for " Mou se Button Re lease," and as you can probably tell, this is pretty much indicating that the mouse button has been released.įollowing the Blue rectangle is the Purple rectangle. You'll notice that the last line says "MSBRL" instead. Most of the lines will say "MULTI" which, to my knowledge, means that the script will be executing something related to a mouse input. As far as I know, this only applies to mouse related functions, with the exception of certain keyboard presses. With that being said, my simple click script was made on an instance of Nox that is 240x420 (small, isn't it?). This rectangle contains the resolution of your Nox instance. This rectangle contains the Script Separator, which I would assume to be a special string that Nox places at the beginning and end of a macro command sort of like bookends on a bookshelf. Take a look at the Black rectangle at the beginning. Let's start with this recording I have of a single click and process it chunk-by-chunk. For these examples, I will be be using Notepad++. I'll give it my best shot here (from what I can understand). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |