"Mouse" jumps when issuing build orders [solved]

[qray]

Hey everyone,

since the latest engine version 88 - though I haven't played with 86 and 87; 85 was fine- playing latest BA 7.68; using IceUI and running on linux in full screen mode:

I hope I manage to describe the problem in an understandable way:
Sometimes (annoyingly often to be honest), when I issue a build order, the place the building is to be done is not where I clicked but jumps to some place far away. Happens only sporadically, so I found no way yet to reproduce. The place it jumps to is also not "always on the right bottom corner of screen" or something but randomly distributed over the map. Happens with low load and at game fully running with many units (high load).

Anybody any idea what I can try to solve this? I played around with switching off and on widgets which I suspected, but that didn't help so far....
I am open for ideas, my mates are already annoyed of my constant swearing during the game

Thanks in advance,
Ray

[knorke]

seems too obvious, but maybe it is the "mex snap" widget?
test with default stuff (no ice ui, only default widgets etc)

[qray]

Thx for the tip.

"Mex Snap" was already disabled, so unfortunately it is not that easy

test with default stuff (no ice ui, only default widgets etc)

I'll try to play with a cleaned "spring/LuaUI/Widgets" next time. Would be a pity if it was IceUI, though.

[qray]

Quick update: problem seems to be solved.

I cleaned my widget directory (was quite full with stuff, I didn't use or needed any more) -> no problem any more.
I have to admit, I noticed that "Use Hardware cursor" was un-ticked and I switched it to on at the same time (bad error tracking approach doing two changes at once, I know ). Could this also have been the cause?

Then copied back IceUI -> still no problem.
So I copied back the very few additional widgets which I actually really want to have -> still good.

So I'll try in future games if it might have been the "hardware cursor: off" setting.
If not, maybe I'll try step-wise which other widget might have caused the problem.