Gmoccapy - added more LOG.debug

[zz912]

I am makeing it still again, again, again.
So I made PR.

[hansu]

I think this should better go into master

[zz912]

I would like to ask you to consider merge it to branche 2.9.

Reasons:

• Gmoccapy in branch 2.9 still shows strange random behavior in the tool change area even with automatic G43 deleted. These notes might help other users in finding the source of the bug.
  I have done a retrofit from version 2.9 and I don't want to go to version 2.10 if there is only need to find bugs (maybe my bugs, maybe LCNC bugs) related to ATC.
• branche 2.9 is still a STABLE version and is used for comparison when looking for bugs in other versions. Therefore, I want the same messages in 2.9 and in 2.10
  For example here:
  2.10 Gmoccapy - remap M61 disable show MDI window #3120
• I don't think this PR is so dangerous that it can't be merged until 2.9

[gmoccapy]

I agree with hansu,
This changes are to be merged to master.

• Changing of a behavior of a GUI and therefor the machine in a stable release is not good to do.

Norbert

[zz912]

I added only LOG.debug for better description of bugs in 2.9. How did I changed behavior?

[andypugh]

I am undecided on where this should go. I don't think that it actually changes the GUI behaviour, but at the same time it isn't quite a bugfix.

Does it have any effect on the "runtests" stage? Tests tend to compare terminal output. But given that the checks have passed (which include running the tests) I assume that it hasn't changed anything there.

So, I have no real opinion, but don't object to it going into 2.9.

[gmoccapy]

After the "misbehavior" has been fixed all the debug output is not needed any more.
I vote to not include the addinonal outputs at all.

But it is just my opinion and I have not checked the latest changes done in gmoccapy

[zz912]

Software without bugs is just poorly tested software. :-D