Porblem selecting text in paper space

[M.Lindell]

Hello,
I have text in paper space and if I try to select it on first click it starts area selection and I have to click second time or press ESC to finally select text.
To edit text I have to doubleclick twice (first to select and second to edit).

This happens only in paper space if TEXTGAPSELECTION is set to "1". If it's set to "0" everything works normally.

What would be the problem here? I would like to keep TEXTGAPSELECTION set to "1", but it's a bit annoying in paper space. I'm using AutoCAD 2021 on windows 10.

[imadHabash]

Hi,

i suggest to make a small screencast that will help us more to understand your issue ? 

[M.Lindell]

Here's the screencast

[M.Lindell]

New try with screencast:

[RobDraw]

Cannot recreate the problem by changing TEXTGAPSELECTION.

Can you share the problem file?

[imadHabash]

would you turn OFF your hardware acceleration from GRAPHICSCONFIG command , any changes ?

[M.Lindell]

No changes if hardware acceleration off....

[imadHabash]

in your previous screencast i noticed that your below icon for hardware i turning OFF and ON !!! 

if you don't mind ... waht happen if you change your mouse with another one ? 

[M.Lindell]

The harwarea acceleration icon seems to turn dim during area selection. No idea why.
(in model space too)
Tried different mouse and it's the same. 

My collague doesn't have this issue so I think I'll reinstall.

[RobDraw · Accepted solution]

---

@M.Lindell wrote:

My collague doesn't have this issue so I think I'll reinstall.

---

Make sure to follow Autodesk's directions on doing a full uninstall.

[imadHabash]

>> My collague doesn't have this issue so I think I'll reinstall.

how about Install the latest driver for the graphics card in the system . >> Click << 

[M.Lindell · Accepted solution]

@imadHabash @RobDraw 
I may have figured out what caused the issue.

I had PICKAUTO set to value "7". This combined with TEXTGAPSELECTION = "1" caused the problem.
 - Changing the PICKAUTO to 5 in 2021 version fixed the issue.

In 2022 version I couldn't recreate this issue.