![]() It is actually an issue with how the games were programs. Obviously the main flaw of it being that it was reset but the timer was still accurate and didn't differ between systems. the original IBM PC did have a rather accurate Real Time Clock. Many years ago before real-time timers the faster the computer the faster the program executed such as games that would start and Pac-Man ghosts would immediately catch Pac-Man upon starting an 8088 8-bit DOS game on a 486DX33Mhz. BUT I thought there should be a real-time timer that should keep it all in sync no matter the speed of the computer. My time is valuable to me.LOL) Maybe i should try running that macro in XP compatability, but I think it has to do with the CPU being too fast. ( Yes this could be considered cheating, but it doesnt give me any advantage over the other players other than not having to waste time out of my day in the grind portion of it. This then only requires less than 30 minutes of game play vs 3 hrs at the computer daily to enjoy the better aspects of the game vs the boring grinding. ![]() I then can come back to my computer later in the day and use the ( money/skill credit ) to strengthen my army and become powerful and conquer the virtual realm as a heavy hitter. I dont have 2 hrs a day to burn up the (energy) in dedundant fighting in the game to convert it to other forms of value within the game so I have a batch file that performs a ping ( for 5 sec delay ) then starts the macro.exe over and over again until the energy is used up. Figured I'd check to see if anyone else has used this software and ran into same issues with rate of macro instruction execution? Currently using it to automate a very redundant portion of an online game on facebook. Maybe I just need to run this automation on my slower CPU systems. Went to their website and downloaded newer version and tried that and still same issue. Decided to run this software on my faster Windows 7 system with Athlon II x4 620 2.6Ghz CPU and 4GB RAM, and I have noticed that there is a slight issue with playback of the macro EXE executing slightly faster than the actions recorded. PS: The windowfocus command is required for most other commands to work.I have been using this JitBit Easy Macro Recorder for about 6 years now on slower ( Pentium 4 -> Core 2 Duo ) computers to run quick to create and use automated keyboard/mouse routines. If you change your desktop settings such as font size or reinstall your system, they might stop working and would require adjustment. Of course, although such scripts are much more robust than recorded macros, they are by no means portable. a defined window size (if click points change with different sizes).the window id (only if your window title is not unique).Start Sakura with the custom name xdowindow and start the xdotool script in it: sakura -t xdowindowįor your own script you would need the following: The sleep commands are just to slow it down to a watchable speed. I tried to get this working with gnome-terminal but gnome-terminal has been a major failure for some time and since then its window title cannot be changed, so I used Sakura for testing instead. This is a sample script for xdotool: search -name xdowindow ![]() You would have to calculate the offset.Ĭreate a text file for your xdotool script. Keep in mind that on Ubuntu you usually cannot move your window to the coordinates 0,0. Xterm -hold -e /usr/bin/xdotool getmouselocation ![]() To get the right position for your clicks you can move your window into the top left corner and use: ALT+F2 You can even execute commands from within a pure xdotool script and close their window after the job is done. With xdotool could identify windows and manipulate them to your parameters, and then program clicks relative to them, ignoring their position. I know this may not be what you are wishing for but it may be the best solution.Ī recorded macro would fail with missing windows, different window sizes etc. It gives you far more control over the process.įrom your description, I assume that you need something more permanent and not a macro that is only used a few times after recording it. Instead of recording a macro, it might be more useful to script it from scratch with xdotool. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |