<?xml version="1.0" encoding="utf-8" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
<title><![CDATA[Perfect Macro Recorder comments:]]></title>
<link>https://www.giveawayoftheday.com/perfect-macro-recorder/</link>
<description><![CDATA[free licensed software daily]]></description>
<language>en</language>
<lastBuildDate>Wed, 03 Feb 2010 13:20:52 +0000</lastBuildDate>
<atom:link href="https://www.giveawayoftheday.com/perfect-macro-recorder/feed/" rel="self" type="application/rss+xml"></atom:link>
<sy:updatePeriod>hourly</sy:updatePeriod>
<sy:updateFrequency>1</sy:updateFrequency>
<generator>FeedWriter</generator>
<item>
<title><![CDATA[By: martin]]></title>
<link>https://www.giveawayoftheday.com/perfect-macro-recorder/#comment-106884</link>
<description><![CDATA[@caulbox

I apologize if you took any offense by my comment, I meant only to provide an immediate review of the product.

Given your reply, I elected to give TinyTask 1.22 another try and, as you point out, I found the COMPILE button and, upon creating the executable, I fully retract my statement that GUI is a nuisance.  

However, I also fully stand by my statment that, given its SLOW speed (relative to AutoHotKey and similar to Perfect Macro Recorder), I prefer to pass on TinyTask.

That all being said, as I mentioned in my previous posting, its nice to find a stand alone program (no Registry entries).  Accordingly, I shall keep a copy of TinyTask 1.22 on my USB drive as a portable utility.  

Thanks again, caulbox.

Regards,

Martin]]></description>
<pubDate>Wed, 03 Feb 2010 08:20:52 -0500</pubDate>
<guid isPermaLink="false">https://www.giveawayoftheday.com/perfect-macro-recorder/#comment-106884</guid>
<dc:creator><![CDATA[martin]]></dc:creator>
</item>
<item>
<title><![CDATA[By: Francis Carden]]></title>
<link>https://www.giveawayoftheday.com/perfect-macro-recorder/#comment-106883</link>
<description><![CDATA[For those interested, the other major advantages for “injection” v “playback” automation technologies, I see daily, are;

1. parrallel-tasking – by not relying on screen/mouse positions, keyboard simulation nor dependent of screen resolution or focus, you can drive apps one at a time or all at once (if the app allows it). You can send 3 apps to complete a task in one automation and wait for all three to finish before say, using a single thread to continue another!

2. Long time running batch processes. Can be run for days, even weeks and wake up when something occurs in the app!

3. Apps and automations can be stuck on a virtual machine and run 100% unattended (and or hidden). They can even expose a new API (service) of the automation itself for others to call into remotely on demand. (Great for moving automations and apps to a “server” side model.

4. Can work with multiple copies of the same app at the same time. Automation tools often get confused if apps “look” the same on the screen. Injection knows the app and the objects relative to the “instance” of the app, regardless of number of instances and can control any one or all of them in context.

5. Monitoring. Injection allows you to detect when a user or the application has done something that might then determine an automation going off in another direction. Or even notify someone something has changed in the app or drive another automation on another machine!

6. You can automate applications with hidden controls, tabs, MDI Modal and Modeless forms/objects. Injection see’s all. Most automation software relies on visibility to read/perform a function.

7. Getting data out of an object that is only partially visible. Since injection see’s an objects full properties, it can see the entire (even wrapped) text from a text box, or a specific color of a control or a selected item in a list box that’s not even shown!

8. Timing. This is one of the biggest, a lot of automation software breaks because you often have to rely on sleeps and waits. True injection can wait as long as it takes (mins, hours or weeks) for an object to appear and then continue.

Bottom line, I love automation software of any kind if they do the job reliably or at least save time. (Even unreliable automations are fine if you know they are and can sit and watch and correct on the fly. However, injection automation is really for enterprise ready processes that you must rely on and/or you want to use in significant production environments.

Open for other debate. The good news is, there are products for everyone. Free and not so free.

Francis Carden, Founder, OpenSpan Inc.,]]></description>
<pubDate>Tue, 02 Feb 2010 16:31:16 -0500</pubDate>
<guid isPermaLink="false">https://www.giveawayoftheday.com/perfect-macro-recorder/#comment-106883</guid>
<dc:creator><![CDATA[Francis Carden]]></dc:creator>
</item>
<item>
<title><![CDATA[By: Francis Carden]]></title>
<link>https://www.giveawayoftheday.com/perfect-macro-recorder/#comment-106882</link>
<description><![CDATA[Automation tools in general are about emulating user activity by relying on simulating keystrokes when everything is setup correctly in the first place. The more expensive products (as mentioned, like OpenSpan) use injection technology.

i.e. they inject into the run time of the application giving ‘extreme’ robustness to the automations. However this is required for the markets they serve, which is primarily to automate tasks whilst a user is actively working with the applications they use. Most automation tools are more like “set it all up”, “ready”, “set”, “go”. i.e. a lot of unattended operations or exact repetitive tasks.

Injection technology gives you access to the underlying objects themselves, and gives you the same/similar control as if you were the original developer of the app (even if you don’t own source code). All properties, methods and events of those objects are available to you. You can even prevent users from clicking stuff by intercepting a click (until something else is ready) or you can set it’s hide property so the user can’t even see it until you are ready. That level of injection means you can also wait for a real event, like an object to be created inside the app, or a text change event of window create, created, destroyed, or destroying events. Again, this level of robustness means you can build robust automations in mission critical apps and guarantee the success (or failure) of a process.

I’ve only touched at the surface here but I’ve been involved in automation technology of every kind since I was 20 (macros) and since I am now 46, love talking about and happy to help. This is all great discussion.]]></description>
<pubDate>Tue, 02 Feb 2010 16:30:38 -0500</pubDate>
<guid isPermaLink="false">https://www.giveawayoftheday.com/perfect-macro-recorder/#comment-106882</guid>
<dc:creator><![CDATA[Francis Carden]]></dc:creator>
</item>
<item>
<title><![CDATA[By: caulbox]]></title>
<link>https://www.giveawayoftheday.com/perfect-macro-recorder/#comment-106881</link>
<description><![CDATA[#26 Martin
<cite>Unless I am missing something here, the fact that TT 1.22’s GUI opens, whenever the specific .rec file is executed, is a nuisance in my opinion. TT 1.22 is also very slow compared to AutoHotKey, and a bit slower than Perfect Macro Reader.</cite>
 
I was really 'recommending' TinyTask, more as a demonstration of what is possible with <i>unbelievably</i> minimal programming, rather than a serious contender for it's full featured rivals.
 
That said, TinyTask most certainly has it's uses. You can eliminate the GUI nuisance by compiling and running an executable (exe) program file, rather than loading a (.rec) saved recording.
 
Not sure if I understand what you mean about very slow speed? In my experience, TinyTask seems to replay it's recordings in real time accord, with the time I might have taken whilst recording. There's an option to play at fast speed, but I prefer not to use it (or only very rarely). I find that mouse clicks often don't comply with what was intended when the speed is rushed too much.]]></description>
<pubDate>Tue, 02 Feb 2010 01:30:56 -0500</pubDate>
<guid isPermaLink="false">https://www.giveawayoftheday.com/perfect-macro-recorder/#comment-106881</guid>
<dc:creator><![CDATA[caulbox]]></dc:creator>
</item>
<item>
<title><![CDATA[By: allhadis]]></title>
<link>https://www.giveawayoftheday.com/perfect-macro-recorder/#comment-106880</link>
<description><![CDATA[How secure is a Macro recorder if it records your moves ??]]></description>
<pubDate>Tue, 02 Feb 2010 00:34:07 -0500</pubDate>
<guid isPermaLink="false">https://www.giveawayoftheday.com/perfect-macro-recorder/#comment-106880</guid>
<dc:creator><![CDATA[allhadis]]></dc:creator>
</item>
<item>
<title><![CDATA[By: martin]]></title>
<link>https://www.giveawayoftheday.com/perfect-macro-recorder/#comment-106879</link>
<description><![CDATA[@david

If your "anykey" is AnyKey Simple Shell 1.20, then its no longer freeware - its shareware.  

http://download.cnet.com/AnyKey-Simple-Shell/3000-2379_4-10369196.html

On the other hand, if its NOT AnyKey Simple Shell then I would be obliged if you would share the manufacturer's or developer's URL.

Thanks,

Martin]]></description>
<pubDate>Mon, 01 Feb 2010 23:50:55 -0500</pubDate>
<guid isPermaLink="false">https://www.giveawayoftheday.com/perfect-macro-recorder/#comment-106879</guid>
<dc:creator><![CDATA[martin]]></dc:creator>
</item>
<item>
<title><![CDATA[By: Unbeatable Freebie Hunter]]></title>
<link>https://www.giveawayoftheday.com/perfect-macro-recorder/#comment-106878</link>
<description><![CDATA[Lol!!


Today's giveaway looks promising but this FREEBIE is definitely better:


http://www.mydigitallife.info/


What do you make of it guys?

Enjoy!]]></description>
<pubDate>Mon, 01 Feb 2010 22:18:59 -0500</pubDate>
<guid isPermaLink="false">https://www.giveawayoftheday.com/perfect-macro-recorder/#comment-106878</guid>
<dc:creator><![CDATA[Unbeatable Freebie Hunter]]></dc:creator>
</item>
<item>
<title><![CDATA[By: aRenegade]]></title>
<link>https://www.giveawayoftheday.com/perfect-macro-recorder/#comment-106877</link>
<description><![CDATA[@#1 ashraf in your “bad” you wrote:

<i>* Has a few bugs.</i>
That’s like asking someone for a home address and getting “North America” for an answer.

<i>* Mouse activity is based off coordinates instead of program/window recognition.</i>

So why is that a bad thing? Using coordinates to track mouse activity has been the standard since the invention of the mouse. I would ask if you could give an example of this program/window recognition thing you’re referring to.

<i>* Impractical means of editing macros.</i>

Why and what’s so impractical about it? I found editing macro’s with today’s GOTD, Perfect Macro Recorder, to be easy, and not at all impractical. It couldn’t be much simpler.]]></description>
<pubDate>Mon, 01 Feb 2010 21:54:31 -0500</pubDate>
<guid isPermaLink="false">https://www.giveawayoftheday.com/perfect-macro-recorder/#comment-106877</guid>
<dc:creator><![CDATA[aRenegade]]></dc:creator>
</item>
<item>
<title><![CDATA[By: me]]></title>
<link>https://www.giveawayoftheday.com/perfect-macro-recorder/#comment-106876</link>
<description><![CDATA[Excuse my ignorance, but what is the purpose and/or point of such a program?]]></description>
<pubDate>Mon, 01 Feb 2010 19:13:32 -0500</pubDate>
<guid isPermaLink="false">https://www.giveawayoftheday.com/perfect-macro-recorder/#comment-106876</guid>
<dc:creator><![CDATA[me]]></dc:creator>
</item>
<item>
<title><![CDATA[By: JKEngineer]]></title>
<link>https://www.giveawayoftheday.com/perfect-macro-recorder/#comment-106875</link>
<description><![CDATA[I have had fairly good results with MacroMaker. (Not today's offering.)It's available on many of the software download sites. It is coordinates based, with all that everyone has implied about that.  It requires that things be in the same place each time.  

For much of my use that does not matter.  I usually create a macro by recording an action that I need to perform many times at the time I record it, such as modify multiple pages in a report.  (not search and replace) After recording a macro, I test it on the same instance I recorded or on the next one.  I include advancing to the next one as part of the macro.  The macro can be edited, but not too easily.  A big advantage is that the macro playback speed can be adjusted in the program.  Once I am satisfied with the action, I speed it up about 10x, so it's way faster than I am!

Another program I stumbled on yesterday looks like a real winner based on the web description.  It's called Sikuli and it is graphic based.  Per the demos it will execute programs, key presses, etc.  It will also "look" for a part of the screen, that is an image on the screen such as a button, and go to it and press it.  It's an MIT program, and is at http://groups.csail.mit.edu/uid/sikuli/ 

JK]]></description>
<pubDate>Mon, 01 Feb 2010 19:09:38 -0500</pubDate>
<guid isPermaLink="false">https://www.giveawayoftheday.com/perfect-macro-recorder/#comment-106875</guid>
<dc:creator><![CDATA[JKEngineer]]></dc:creator>
</item>
</channel>
</rss>