Read the statement by Michael Teeuw here.
Cursor shown in v2.16.0
-
@sdetweil I see the cursor only on the pi. And it disappears if I move the mouse the first time on the pi. But the cursor is visible again after i do a
pm2 restart 0
On my windows machine witch chrome, I don’t see the cursor at no time.
-
@majorc so, that confirms it’s an electron issue.
you could change to run server mode with chrome on the pi.
-
@majorc said in Cursor shown in v2.16.0:
Or do I have to wait for version 17?
In v2.16.0 we have electron v11, in current develop branch (which will become v2.17.0 in October) we have upgraded to electron v13.
-
so u can try develop, but there is no guarantee that is is fixed there
-
could fix the black cursor with an entry in
custom.css
:html { cursor: none !important; }
Can you test if this works on your side? If so we should change this in
main.css
(will provide a PR then). -
@karsten13 said in Cursor shown in v2.16.0:
Hi Kasten,
I tried !important in the custom.css and in the main.css. The cursor is still visible.
Even after after a reboot of the pi, the same, still visible.I think I will wait for v2.17.0 in October.
-
The cursor is still visible.
:(
tried yesterday on my pi3:
- v2.16.0: no cursor
- v2.17.0-develop: black cursor
- v2.17.0-develop with css
cursor: none !important;
: no cursor
So waiting on v2.17.0 is no solution.
Another idea is to simulate a cursor movement on electron start.
-
can you try to patch the file
js/electron.js
for a test, please add the following at line 74:mainWindow.webContents.on('dom-ready', (event)=> { mainWindow.webContents.sendInputEvent({type: "mouseMove", x: 0, y: 0}); });
Does this hide the black cursor?
(I changed the code here again …)
-
@karsten13 said in Cursor shown in v2.16.0:
Like so?
// Open the DevTools if run with "npm start dev" if (process.argv.includes("dev")) { if (process.env.JEST_WORKER_ID !== undefined) { // if we are running with jest var devtools = new BrowserWindow(electronOptions); mainWindow.webContents.setDevToolsWebContents(devtools.webContents); } mainWindow.webContents.openDevTools(); } // Set responders for window events. mainWindow.webContents.on('dom-ready', (event)=> { mainWindow.webContents.sendInputEvent({type: "mouseMove", x: 0, y: 0}); }); mainWindow.on("closed", function () { mainWindow = null; });
That works perfekt! Thank you so much!
-
@majorc o.k., then I will provide a PR for this in the mm repo