[BUG] Broken PAUSE_PROBE_DEPLOY_WHEN_TRIGGERED

[prophetmaster]

Did you test the latest bugfix-2.0.x code?

Yes, and the problem still exists.

Bug Description

pause before probe not working in right direction inverted...

replace this -> if (deploy == PROBE_TRIGGERED()) break;
by -> if (deploy != PROBE_TRIGGERED()) break;

Bug Timeline

No response

Expected behavior

No response

Actual behavior

No response

Steps to Reproduce

No response

Version of Marlin Firmware

2.0.9.1

Printer model

custom delta

Electronics

No response

Add-ons

No response

Your Slicer

No response

Host Software

No response

Additional information & file uploads

No response

[ellensp]

Please update (bug summary) to related issue

[ellensp]

really? perhaps I was not clear.
Please change the title to describe the actual bug. not literally using that string.

[thisiskeithb]

Since you've provided a fix, it'd be faster if you submitted a Pull Request so it can be reviewed.

[thinkyhead]

Hey! It took me less than 5 minutes to get this patched. If a solution is very simple, let's not badger the submitter for clerical fixes and post comments asking for a PR that might never come. Admins can just post a PR and this gets the issue closed ASAP so it doesn't linger for 9 days or more. If you require extra permissions to be able to edit issue titles please let me know.

[thisiskeithb]

Hey! It took me less than 5 minutes to get this patched. If a solution is very simple, let's not badger the submitter for clerical fixes and post comments asking for a PR that might never come. Admins can just post a PR and this gets the issue closed ASAP so it doesn't linger for 9 days or more. If you require extra permissions to be able to edit issue titles please let me know.

I didn't feel comfortable submitting a fix for something that I couldn't verify was broken. That's why I generally ask the person who had the issue & fix, to submit a PR.

[thinkyhead]

I reviewed with Sublime Merge the last changes to the relevant lines and saw that indeed, the logic had been done backwards, and that was enough to confirm the fix.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.