now THAT sounds interesting, especially since I've been coding in Python a lot these last couple of years.

-mouser (January 03, 2025, 12:49 PM)

Could be a great fit then! :) I've tried using OpenSCAD for projects but once things got complex I got stuck, something about the syntax and structuring of code, so I ended up back with GUI CAD solutions. But I know people who say CadQuery is an improvement so I plan to give it a shot. There's also a fork called build123d
https://github.com/gumyr/build123d
https://github.com/phillipthelen/awesome-build123d
https://github.com/CadQuery/cadquery
https://github.com/CadQuery/awesome-cadquery

In my FARR installation there are scoring rules stored in
C:\Users\<username>\Documents\DonationCoder\FindAndRunRobot\FindAndRunRobot.ini
in the sections [HeuristicScoring] [PatternScoring] and [SearchFolders]

The .alias files also contain per alias scores at
C:\Users\<username>\Documents\DonationCoder\FindAndRunRobot\AliasGroups\MyCustom\myaliases.alias
and possible other nearby .alias files

Ok so there might be two issues, though related, if I understand you correctly?
1. FARR crashes (the FARR process closes) when you switch between physical monitors.
2. After FARR has crashed (the process is closed) starting FARR again fails if the FindAndRunRobot.ini item "MainLeft" has a negative value, which FARR automatically adds after 1 happens.

With switching you mean something like pulling out the HDMI cable of one monitor and inserting that of another while the PC is on?

Some idea on things you could test to narrow down the issues further:

Does these things happen every time you switch physical monitors? Or only sometimes? If sometimes, does it depend on how the monitors are positioned (in Windows) or on which monitor is primare? Does it depend on which monitor FARR is showing on?

I can't be of help with examining crash reports, only mouser can do that I think.