[Problem] CAM: Milling simulation continuously stealing window focus and releases it

[FreeCAD-Bug-Importer]

Issue imported from https://tracker.freecad.org/view.php?id=3714

• Reporter: @sleeply4cat
• Date submitted: 12/5/2018
• FreeCAD version: 0.18
• Category: Bug
• Status: assigned
• Tags: #post-to-forum, Path

Original report text

When Path simulation is running, FreeCAD continuously takes window focus for a short time and then releases it. It makes the whole system unresponsive.

Additional information

Checked on Ubuntu 18 Cinnamon/Ubuntu 18 Gnome.
xev log:

    mode NotifyGrab, detail NotifyNonlinear

FocusIn event, serial 37, synthetic NO, window 0x3e00001,
    mode NotifyUngrab, detail NotifyNonlinear

KeymapNotify event, serial 37, synthetic NO, window 0x0,
    keys:  2   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   

FocusOut event, serial 37, synthetic NO, window 0x3e00001,
    mode NotifyGrab, detail NotifyNonlinear

FocusIn event, serial 37, synthetic NO, window 0x3e00001,
    mode NotifyUngrab, detail NotifyNonlinear

KeymapNotify event, serial 37, synthetic NO, window 0x0,
    keys:  2   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   

OS: Ubuntu 18.04.1 LTS
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.18.15302 (Git)
Build type: Release
Branch: master
Hash: 2e03d2f298677b8212c22cbbc3cb20b7c80eabb5
Python version: 2.7.15rc1
Qt version: 4.8.7
Coin version: 4.0.0a
OCC version: 7.3.0
Locale: English/UnitedStates (en_US)

Steps to reproduce

1. Open FreeCAD
2. Create a sample object
3. Select Path workspace
4. Create a job with some pathes
5. Start a simulation
6. Open another window (Gedit, for example)
7. type '1234567890', something like '156780' will appear

Other bug information

• Priority: normal
• Severity: minor
• Category: Bug
• OS: Ubuntu 18.04.1
• Platform: Linux
• Updated: 2/6/2021

Discussion from Mantis ticket

Comment by Kunda1 2018-12-05 13:23

heads up sliptonic mlampert

---

Comment by sliptonic 2019-01-23 00:38

shaiseger Do you have anything to add?

---

Comment by Kunda1 2020-01-08 18:18

shaiseger ping

[luzpaz]

@sliptonic is this something using camiotics will solve?

[sliptonic]

It will be one more tool in the simulation and visualization toolbox. Camotics simulation is much more mature than the FreeCAD native version but it is 3 Axis only for now.

[shaise]

This issue was apparent from day one and it bugged me as well. I just do not know how to do it differently.

[luzpaz]

This reminds me of the TestWB issue. If you run a general test the focus continually gets pulled back to the tests and it's not possible to get much done (unless you're on dual monitors and can mouse click quickly 🤣 )

[luzpaz]

@sliptonic now that we're offloading the heavy lifting to camotics, does it happen with camotics as well ?

[sliptonic]

They're pretty different things. I'm planning to do a video on the Camotics thing.

[luzpaz]

They're pretty different things.

I suspected that. It may be still of interest to keep this ticket open as it is not a phenomena that is just associated with the soon to be legacy FreeCAD milling simulation. It also occurs when running the Test WB.

[xtemp09]

I've failed to reproduce the problem described.

The MainWindow becomes a bit unresponsive, though.

Ubuntu 22.04.3 LTS

OS: Ubuntu 22.04.3 LTS (KDE/plasma)
Word size of FreeCAD: 64-bit
Version: 0.22.0dev.34784 (Git)
Build type: Debug
Branch: main
Hash: 61c1b2bfc2339b272d3fa44bb9dbb6bdba528a64
Python 3.10.12, Qt 5.15.3, Coin 4.0.0, Vtk 9.1.0, OCC 7.5.1
Locale: Russian/Russia (ru_RU)

[luzpaz]

I've failed to reproduce the problem described.

@xtemp09 really ? This has been the behavior of the milling simulation. I don't recall someone fixing this issue. Did i miss something ?

[xtemp09]

@luzpaz, can you reproduce the problem?

[luzpaz]

Sure, can you provide a quick test file ?

[sleeply4cat]

Sure, can you provide a quick test file ?

the bug looks pretty much resolved for me

[luzpaz]

@shaise can you confirm this is fixed ?