Jump to content
Macro Express Forums

joe

Members
  • Posts

    1,002
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by joe

  1. Welcome to the group!

     

    Along with the tutorial, the Quick Wizards are a great place to get started learning Macro Express. Any macro that a Quick Wizard generates can be directly modified in the Script Editor window.

     

    It seems from your post that the simplest solution would be to generate a macro that takes the following steps for each field:

    1. Activate the Lotus window
    2. Tab to a field
    3. Copy it to the clipboard
    4. Activate the web page window
    5. Tab to the target field
    6. Paste from the clipboard

    Keep in mind that other solutions will present themselves as you gain more experience with Macro Express.

     

    As to the book taking a month ... that seems awfully strange to me. When did you order it? Where did you order it from? And where is it being delivered? US? Canada? Europe?

  2. Hello Randall!

     

    Geez ... we thought everybody needed or PGM Functions Library :rolleyes:

     

    Since downloading this playable, and giving it a run-through, I would like to spend more time examining it. It looks interesting.

     

    As to the { DateTime } functions, it is true that they do not yet do anything with time-of-day calculations. Here is a quote from the user's manual that comes with the PGM Functions Library:

    The functions are all based on Julian Day numbers, which are not to be confused with Julian Dates, whose calendar ended on October 15th, 1582 when the Gregorian calendar replaced it. The Gregorian calendar is the reformed Julian calendar with the year fixed at 365 days except for leap years which contain 366 days. Leap years are years that are exactly divisible by 4 except for century years which must also be divisible by 400. This is the calendar in common use today.

    It may be interesting to note that a Julian Day number starts at noon and not midnight as one would expect. ... okay, enough trivia!

  3. Welcome Defender56!

     

    If I understand what you are asking, once you make a change to a macro in a library (.mex) file, and then save the change, there is no way to go back and see what it looked like before. So, there is nothing to compare.

     

    However, there is a 3rd party product that we use, which allows us to go back dozens of revisions and restore any one of them. Its called GoBack. You can read about it on Symantec's web site.

  4. Hello Les!

     

    It is possible that working with a string in this manner can be slower than processing a loop. You are using five lines of "character-by-character" code to get to, and strip, the CR/LF as compared to a single line of code that reads in the string and removes the CR/LF all at once. How big is the string?

     

    Do I understand that you are combining macros? There are no CR/LFs in native Macro Express code. What am I missing?

     

    Also, can you post the native code of the example shown here? It might help.

  5. The Macro Run command is what you want. It works like a subroutine call. Just place those seven lines of code within a new macro and call it.

     

    It will not increase the speed the speed of your macro, but neither should you notice a decrease in speed either.

  6. Welcome to the group!

     

    The Switch / End Switch construct does not loop. It is just a big If / Else / End If tree.

     

    The Ascii File Begin Process and Ascii File End Process command construct will loop through records in a delimited file one record at a time. Each delimited field in the current record is placed in its own variable beginning with the variable that you specify, say T45. All of the processing that you want to do to these variables are placed within the loop (i.e. between the Ascii File Begin Process and Ascii File End Process commands). The default setting for the construct is to begin at the first record in the delimited file and process all records.

     

    If this does not help, then it might be advantageous to post a sample of the macro(s) you have created for this task.

  7. Then something within your macro is resetting the T1 variable to "" (empty).

     

    All variables in Macro Express are global in scope. It does not matter in which level within a chain of callable macros the variable is set or reset. All other macros, up-and-down the calling chain will use the same variable and variable value. In other words, you may have an unlimited number of macros calling other macros, but they will all use the same T1-T99, N1-N99, and D1-D99 set of finite variable tags.

     

    This will be true for as long as the current macro session is running. Once a new macro session is fired, all variables are immediately set back to their default empty or zero values. A macro session starts when a macro, or chain of macros, begins execution and ends when it, or they, stop.

     

    There is a way to pass variable values to the next macro session, but that is a different subject.

  8. Hello K_H!

     

    There was another discussion back in September last year on the subject of Terminal Services. Personally I have found that working macros over thin-nets is tricky but doable. What is seen locally may not be what is displayed on the server, and vice-versa. It is very easy to get confused on whether the host or remote station is doing the work, which means that the macro will get confused. My suggestion is to contact support at Insight Software Solutions to go over your specific macro, and what is going wrong, so they can help you.

  9. If the name of this macro contains the word "winsock", and if it is enabled, and if you attempt to launch the Macro Express editor, then the editor will disappear. Why? Well, based on what you posted, a macro was created that will fire whenever a window that contains the word "winsock" gains focus. The window title of the editor includes the name of the macro that you are editing.

     

    If this is not the case, then more details will be needed.

     

    ---------

     

    To answer your question about me: yes, I am a programmer and a Macro Express user. And although I did write a book about Macro Express, I would not consider myself an author ... so to all of you Anne McCaffreys, Clive Cusslers, Dean Koontzs, and Stephen Kings out there, your jobs are safe.

     

    As to "knowledgeable"; if I know the answer to a question, then yes. If not, then no. In my 30 years of programming, I have learned that there is more of the latter than the former.

     

    ---------

     

    You can do with a HotKey macro what you intended a ShortKey to do. Using your example, simply create one that is activated by Ctrl+G or Ctrl+Shft+G. Inside the macro, use the Text Type command to do whatever the ShortKey would have done.

  10. Hello David!

     

    I read that you cannot change the height of your window, but I was not sure if you meant physically or something else. So ...

     

    One small trick that we have used in the past to get the height of a titlebar is to:

    1. Activate the window
    2. Store its current height
    3. Set the window height to zero
    4. Store the new height (which will only be the titlebar)
    5. Restore the window to its original height from step 2.

    This works with most windows and is super fast.

    Activate or Launch: "Notepad" OR "notepad.exe"
    Variable Set Integer %N1% from Width of Window
    Variable Set Integer %N2% from Height of Window
    Window Resize: Current Win - (Width: %N1%, Height: 0)
    Variable Set Integer %N3% from Height of Window
    Window Resize: Current Win - (Width: %N1%, Height: %N2%)

    <LAUNCHYES3:0:0112Notepad<LAUNCH:notepad.exe><IVAR2:01:09:><IVAR2:02:10:><WSIZE:001N,00000"CURRENT"><IVAR2:03:10:><WSIZE:001N,002N"CURRENT">

×
×
  • Create New...