It looks like you're new here. If you want to get involved, click one of these buttons!
A short time ago I posted about how on Win 7 with KL 0.23.3 I am observing problems - when the Macro Editor is open and you do some KLayout function that opens another dialog window (such as "Move By"), the second dialog window (eg "Move By" dialog) and the Macro Editor both flicker and become unresponsive, and eventually the program crashes. You mentioned you were not aware of that bug because you use KL on Linux, so it must be a Windows thing.
Anyway in an effort to help you track down that bug I have tried a few things.
The crash does happen if you have Macro Editor open and do any of the following functions: (this is not a complete list)
The crash does not happen if you have Macro Editor open and do any of the following functions that open a dialog box: (this is not a complete list)
Anyway, that's just a sampling. It is clear it has issue on some functions but not on others. Perhaps by glancing at this list you can tell what is the common factor that defines one list or the other.
If you need more examples I'd be happy to try the other functions and report which ones exhibit the bug
This prompts a suggestion: Perhaps in a future release, the Macro Editor would have a toggle button that enables/disables debugging mode. When enabled it is as it is now. When disabled however, the running script doesn't stop for any breakpoints, doesn't return focus to the Macro Editor after a script is run, doesn't output to the console, etc. Basically in the latter case the Macro Editor is simply a notepad with "Save" and "Run" features. (Currently I actually use an actual notepad app for this, because of this issue.) Disabling this toggle button would allow much faster running of intensive scripts at the cost of debugging mode.
Just an idea!