Jump to content
Macro Express Forums


  • Posts

  • Joined

  • Last visited

  • Days Won


terrypin last won the day on October 18 2022

terrypin had the most liked content!

Profile Information

  • Gender
  • Location
    East Grinstead, West Sussex, UK

Recent Profile Visitors

1,268 profile views

terrypin's Achievements

  1. After another Win 10 update overnight my desktop background image (whatever it is, solid or other) is cropped and confined to the left half of the screen. And now MX's Explorer window suffers the same behaviour as the script window. A PC restart thankfully appears to have restored my desktop to normal behaviour. But whatever it's done to cause the MX irritation remains. In case it's of help to anyone else I've attached a screenshot showing likely WU culprits:
  2. Many thanks, pleased to hear I can stop searching for other causes! BTW, MX Pro Explorer in contrast has continued to open in the same size and position as it's done for, what, a couple of decades.
  3. Hi all, Just want to exclude MX Pro as the cause of the following odd behaviour. For a few weeks when I now open the Script Editor it always displays in a central medium sized window (space on all sides). Attempts to get it back to its regular (20;year old?) position on the right of my Win 10 screen so far in vain. Anyone seen similar? No big deal - I have a macro that repositions, resizes and sets width of panes - but I fret over unsolved puzzles. 🙂 Terry, East Grinstead, UK
  4. Thanks Alan. I meant this window that can be displayed with F5 (or Debug > Show Variable Values), directly after running a macro with F9 (or Debug > Test Run). But the good news is that your post prompted me to try it again - and it's now OK! Hence my screenshot. Previously I got nothing. One of those glitches, hopefully a one-off 🙂 Terry
  5. Hi guys. Long time since I did much editing in MX Pro, and maybe years since I used this debug tool, so I expect this is down to me... Tried several (working) macros with F9 and then hit F5 (or used the menu), but puzzled to find that does not open the expected window. Terry, UK; MX Pro
  6. I assume you mean Lemming's two sed files (.mex and .zip) from nearly 13 years ago? If so, I was able to download both. What problem are you having.
  7. Thanks Alan. What version? Any evidence the usage has increased recently? I use a lot of delays (probably more than necessary). Much shorter than that being discussed, of course, but this has me wondering if brief CPU surges could affect other work.
  8. I've investigated and pleased to find that I was mistaken. An untypical situation. I'd set it to 40 mins instead of the regular 2 or 3. (Failure to collect wife from railway station more serious than over-brewing my teabag.) Decided to use the simple macro hotkey instead of editing one of my more complex alarms - the sort we discussed recently. Its reminder message was still running when I returned to PC hours later. Thought I'd confirm my assumption that it didn't prevent other macros working. So ran a simple shortkey macro in my text editor. That failed to type its string. And again. But my conclusion was too hasty. That (and several of my scores of shortkey macros) have occasionally been unreliable before. That was the cause! 😉
  9. Thanks, appreciate your taking the time to check. Was that in MX Pro 6.4.01? I'm surprised I haven't noticed this long ago. I was using Timed Delay until recently, but yesterday I set it for a much longer period (40 mins). Frustrated at being unable to run any other macro, so changed it to Delay. May reverse that now.
  10. I've used the ultra simple macro below for years. (Usually to remind me - engrossed on PC - to remove tea bag from freshly poured mug of tea.) But I've just noticed this morning that it was consuming over 12% of my CPU. Must be the Delay command. Perhaps since recent update to version Cannot pursue until I get back later home later but meanwhile wonder if one of you could try it please? Tuesday 18 October 2022, 0928. Variable Set Integer %nMinutes%: Prompt Delay: %nDelay% seconds Variable Modify Integer: %nDelay% = %nMinutes% * 60 Delay: %nDelay% seconds Sound File: Alarm-Classic.wav Text Box Display: <VARIABLE SET INTEGER Option="\x01" Destination="%nMinutes%" Prompt="Enter the time delay required in minutes before the alarm should be heard." Mask="FALSE" OnTop="TRUE" Left="Center" Top="Center" Monitor="0"/> <DELAY Flags="\x01" Time="%nDelay%"/> <VARIABLE MODIFY INTEGER Option="\x02" Destination="%nDelay%" Value1="%nMinutes%" Value2="60"/> <DELAY Flags="\x01" Time="%nDelay%"/> <SOUND FILE File="C:\\Users\\terry\\Sounds\\Sound Effects\\Alarm-Classic.wav" Wait="FALSE" _PROMPT="0x0007"/> <TEXT BOX DISPLAY Content="{\\rtf1\\ansi\\ansicpg1252\\deff0\\deflang2057{\\fonttbl{\\f0\\fnil\\fcharset0 Tahoma;}{\\f1\\fnil Tahoma;}}\r\n\\viewkind4\\uc1\\pard\\qc\\b\\f0\\fs58 %nMinutes% mins\\fs16 \r\n\\par \r\n\\par \\fs58 Finished\\b0\\f1\\fs16 \r\n\\par }\r\n" Left="Center" Top="Center" Width="278" Height="200" Monitor="0" OnTop="TRUE" Keep_Focus="TRUE" Mode="\x00" Delay="0"/>
  11. Yes, both of those work, but to me they were not immediately intuitive. However I suppose they have to support the situation when we want the message to be displayed for a certain maximum time, and then other commands run without the message. Including perhaps other Text Box Display commands.
  12. Thanks guys, appreciate both fast replies. I'll take a look at Task Scheduler if MX doesn't cut the mustard. Without sound (a serious downside) I suppose I could settle for leaving the alert message displayed for those hours. Surprisingly even that did not work on first attempt. I entered an arbitrary value of 18 in the 'Stay on screen for' box, and assumed that the following two-liner would display the message for that time. Sound File: Alarm-Beeps.wav Text Box Display: Action CODE <SOUND FILE File="C:\\Users\\terry\\Sounds\\Sound Effects\\Alarm-Beeps.wav" Wait="FALSE" _PROMPT="0x0007"/> <TEXT BOX DISPLAY Title="Action" Content="{\\rtf1\\ansi\\ansicpg1252\\deff0\\deflang2057{\\fonttbl{\\f0\\fnil\\fcharset0 Tahoma;}}\r\n\\viewkind4\\uc1\\pard\\qc\\b\\f0\\fs72 Action alert\r\n\\par }\r\n" Left="390" Top="485" Width="783" Height="421" Monitor="0" OnTop="TRUE" Keep_Focus="TRUE" Mode="\x01" Delay="18"/> But no, it seems a delay of at least that duration is also needed: Sound File: Alarm-Beeps.wav Text Box Display: Action Delay: 30 seconds Maybe I'm being over fussy? But a regular Text Box Display needs to be manually dismissed before the macro continues. Yet with this option it apparently continues regardless. Enjoy your holiday, Cory.
  13. I may be making heavy weather of this, but although I've used MX Pro's neat alarm macros frequently for years, this one has me struggling to configure. I want a weekly alert every Monday at 1 pm and then every hour until 8 pm that day. Life's too short to re-invent stuff, so has anyone here set an alarm like that please and happy to share? Or is it only possible with multiple macros? BTW, is there still an internal 'sounder' in modern PCs? Like the one that I recall gave coded 'beeps' when boot-up failed due to serious faults? If so, can MX Pro play it, so that I'll still get alerted when my speakers are not switched on?
  14. Alphabetic throughout? Could you post a screenshot please?
  • Create New...