.PL My old versions were 32-bit on another machine? No tests possible with it.
To reinstall I will wait a little longer.
Gerald : The mouse works well, only the positioning of the cursor is a problem. With a low acceleration on the mouse, it's a hassle to move the cursor. With a strong acceleration it goes a little better but as soon as the cursor leaves the graphics area it is at fault. For the moment I have an average acceleration and a big dose of patience
2) I don't remember at all what caused me the problem.
The problem is not related to the mouse because it moves normally in the screen but on the other hand it is as if it was jerky outside the area.
This type of problem I had on my Mac which manages its kernels like ubuntu (or the other way around)
You don't encounter this type of problem on pc because there is no possibility to unpair the windows. You can't put the toolbox in a corner and the work screen in the center.
See if like for the Mac you have the possibility in the display to divide or connect the windows. There may be a glassy apple underneath
@Gérald No change by detaching the windows. I have the impression that Draftsight memorizes mouse movements and when moving slowly, the software renders the exact route, which takes a lot of time; in fact, on a sudden displacement there is no delay. That's why I was looking for a variable that could handle this memorization
A priori it can be a problem of graphics acceleration. A solution would be to disable the graphics card for DraftSight only, I don't know if it's possible / easy on ubuntu.
@.PL there had already been a question for draft on ubuntu previously but I can't find it.
@francish if you uninstall and reinstall, on windows it leaves you with configuration traces, on mac it deletes everything (from maverick or with the help of appcleaner)
Does ubuntu react like Win or Mac on this subject?
I just reinstalled Draftsight on another machine running Ubuntu 14.04 64 bits with a video card and the new drivers. The mouse problem is the same.
After a new search on the forum, I just found a trick (or rather a hack as its discoverer says) before the launch of Draftsight, I unplug the mouse and I plug it back in as soon as the software runs and it works. Thanks to Cyclcahine. For me it's solved.
After a new search on the forum, I just found a trick (or rather a hack as its discoverer says) before the launch of Draftsight, I unplug the mouse and I plug it back in as soon as the software runs and it works. Thanks to Cyclcahine. For me it's solved.