Update 7.4.0 Release Info

[Steve]

What has been added to the update?

New Features:

1. Chaining of math operations whilst declaring INTEGER variables
- 1 | RUN ACTION | DEFINE INTEGER VARIABLE | %INTEGER4%::+%INTEGER1%+%INTEGER2%
- 1 | RUN ACTION | DEFINE INTEGER VARIABLE | %INTEGER%::0::+%STRING%::+%RANDOM_1-50%::*5

2. RUN ACTION DEBUG addition of LOGGER
DEBUG LOGGER will send information directly to the MMM event log
See www.turnssoft.com/conditions.html#debug for information and examples
- 1 | RUN ACTION | DEBUG | logger::INFO::verbose::A verbose informational event
- 2 | RUN ACTION | DEBUG | logger::INFO::An informational event
- 3 | RUN ACTION | DEBUG | logger::WARNING::verbose::A verbose warning event
- 4 | RUN ACTION | DEBUG | logger::ERROR::A error event


3. RUN ACTION DEBUG addition of BACKGROUND COLOR and FOREGROUND COLOR
DEBUG BACKGROUND COLOR changes the back color of the macro window for the session
See www.turnssoft.com/conditions.html#debug for information and examples
See www.turnssoft.com/mmm_colors.html for color names
- 1 | RUN ACTION | DEBUG | BACKGROUND COLOR::Black
- 2 | RUN ACTION | WAIT SECONDS | 1
- 3 | RUN ACTION | DEBUG | FOREGROUND COLOR::LightSeaGreen

4. New condition object 'IDLE'
The IDLE condition evaluates the idle state of the host
See www.turnssoft.com/conditions.html#idle for information and examples
- 1 | IF | IDLE | 10::BREAK::NOKEYS | IS TRUE | MESSAGE PROMPT | IDLE detected (10 sec) (keys ignored)::idle::0
- 2 | IF | IDLE | 20::NOMOUSE | IS TRUE | MESSAGE PROMPT | IDLE Detected (20 sec) (mouse ignored)::idle::0
- 3 | IF | IDLE | %INTEGER% | IS FALSE | MESSAGE PROMPT | IDLE NOT Detected::idle::0

5. New ACTION 'RUN MACRO INLINE'
The RUN MACRO INLINE action runs a saved macro file inline before progressing the macro
See www.turnssoft.com/conditions.html#runmacroinline for information and examples
- 1 | RUN ACTION | RUN MACRO INLINE | D:\Macro\calculate.mmmacro

6. New internal variable %LASTLOG% and %LASTLOGEVENT%
LASTLOG captures the last log entry sent to the internal MMM event log
LASTLOGEVENT capture the last log event type sent to the internal MMM event log

Improvements:
1. The operator value for Integer, string, and decimal variables can be be extended to 99 within the 'Add Condition' dialog
2. Notification via the MMM Event Log when GOTO fails to find a line number/label
3. Fast manual variable assignment. The following syntax is now valid:
- 1 | RUN ACTION | INTEGER::12345678
- 2 | RUN ACTION | STRING1::CATCH%RANDOM%
- 3 | RUN ACTION | DECIMAL2::3.3
- 4 | RUN ACTION | BOOLEAN3::TRUE

Fixes:
1. Fixed an issue where the BOOLEAN object would not display within the object menu of the 'Add Condition' page

[zeak]

Mar 9, 2020 3:37:14 GMT Steve said:

What has been added to the update?

New Features:

1. Chaining of math operations whilst declaring INTEGER variables
- 1 | RUN ACTION | DEFINE INTEGER VARIABLE | %INTEGER4%::+%INTEGER1%+%INTEGER2%
- 1 | RUN ACTION | DEFINE INTEGER VARIABLE | %INTEGER%::0::+%STRING%::+%RANDOM_1-50%::*5

Hi Steve,

This doesn't seem to extend to DECIMAL VARIABLE, is there a possibility of including that?

[Steve]

Hmm yep i'll look into it.

Thanks zeak

[zeak]

Also I've tried using the IDLE action but it looks like I would have to have that line in between every other line for it to work, which can be quite a lot when dealing with mouse movement commands.

Is there a way we could have the IDLE integrated into over all macro program as an option that you can turn on.

[Steve]

Apr 6, 2020 2:47:41 GMT zeak said:

Also I've tried using the IDLE action but it looks like I would have to have that line in between every other line for it to work, which can be quite a lot when dealing with mouse movement commands.

Is there a way we could have the IDLE integrated into over all macro program as an option that you can turn on.

What are you trying to do with IDLE that's not working for you? Post an example in a new thread on the questions and help board minimousemacro.proboards.com/board/3/help and we'll nut it out.

[ak]

I love the new RUN MACRO INLINE - much cleaner and more readable than the old FOR EACH LINE IN..

Is there any functional difference between this new action and the old way of doing it?

[Steve]

Jun 8, 2020 19:41:41 GMT ak said:

I love the new RUN MACRO INLINE - much cleaner and more readable than the old FOR EACH LINE IN..

Is there any functional difference between this new action and the old way of doing it?

RUN MACRO INLINE was added to be exactly how you said it 'more cleaner and readable than FOR EACH LINE IN RUN'. Under the hood RUN MACRO INLINE and FOR EACH LINE IN RUN call the same function code but they don't run the same. RUN MACRO INLINE is faster than FOR EACH LINE because it doesn't carry the overhead that FOR functions do. The RUN MACRO INLINE action is the preferred way to read in and execute .mmmacro files inline.

[ak]

That's terrific. Really appreciate you constantly improving this software and listening to user's feedback.