Welcome guest. Before posting on our computer help forum, you must register. Click here it's easy and free.

Author Topic: windows 3.11 recorder  (Read 6087 times)

0 Members and 1 Guest are viewing this topic.

tftnbw

  • Guest
windows 3.11 recorder
« on: July 06, 2010, 09:50:02 AM »
Is there anyway to step through a .rec file while it is running on WFW 3.11?  Also, does anyone know of a program which will translate the .rec file into readable code?

BC_Programmer


    Mastermind
  • Typing is no substitute for thinking.
  • Thanked: 1140
    • Yes
    • Yes
    • BC-Programming.com
  • Certifications: List
  • Computer: Specs
  • Experience: Beginner
  • OS: Windows 11
Re: windows 3.11 recorder
« Reply #1 on: July 06, 2010, 10:43:33 AM »
Is there anyway to step through a .rec file while it is running on WFW 3.11?  Also, does anyone know of a program which will translate the .rec file into readable code?

Don't know about stepping through it, but I do know that the old Windows recorder had a secret way to view the various instructions it contained.

To use this undocumented feature, open the Recorder window with a macro file loaded. Highlight the name of the macro you wish to examine. At this point, if you pull down the Macro menu and click Properties, you ordinarily see a dialog box with settings for that macro: the hotkey combination it uses, whether it uses mouse events or not, and so on.

But, if you hold down the Shift key while clicking Macro->Properties, a completely different dialog appears.This is the Macro Events dialog box, which lists every keyboard and mouse event contained in the macro. This includes every key-up and key-down action, and the name of the program in which these actions took place. Additionally, the list contains the amount of time between each keystroke. (this timing information is not used when the macro is played back unless you specify "Playback speed:As recorded")


if you find a error in the sequence, you will still need to re-record the entire macro, but this hidden feature of the recorder may make finding such an error a lot quicker.
I was trying to dereference Null Pointers before it was cool.