QLeader with MText does not honour MText Line Spacing setting

[anovelli]

How do I get the QLEADER to generate the MTEXT with the Line Spacing Set to EXACTLY. Currnet the line spacing is set yo AT LEAST. I have tried setting the variable TSPACETYPE to 2. This will generate MTEXT with line spacing set to EXACTLY but not MTEXT that is aprt of a QLEADER, I need to know how to get the MTEXT portion of a QLEADER to generate with the line space set to EXACTLY not AT LEAST.

[Mike.Perry]

Hi

I think you may well have found a "bug" with the QLeader command

System variable TSpaceType is not honoured within MText generated via the QLeader command (it can be altered afterwards but that's not the point here).

What you describe is definitely true for AutoCAD 2002.

What version are you running?

Could someone please confirm how AutoCAD 2004 & 2005 handles this issue.

If it turns out to be a "bug" can I suggest that you send a message to CADalyst Bug Watch + post a Wish List Item

Have a good one, Mike

[Glenn Pope]

It still dose this in 2005.

[anovelli]

This issue has been reported to Autodesk. It is a bug. The settings are hard coded into the QLEADER command. Hopefully they will fix it. It happens in AutoCAD 2000, 2002, 2004, & 2005.

[Mike.Perry]

Hi

Can you please add something suitable to the Wish List Forum

+

Send something suitable to CADalyst Bug Watch

I just believe the more places that issues like this are documented the better chance we (Autodesk Users) have of getting Autodesk to act on them.

Have a good one, Mike

[Mike.Perry]

Hi

Just posting back for info....

CADalyst Bug Watch (Feb 2005) - Not Exactly (2000 to 2005 SP1)

http://aec.cadalyst.com/aec/article/....jsp?id=146833

Mike

[Chris.N]

anyone know if this has been addressed in ACAD2007? it's still a pain in 2006.... (thankfully i've figured out how to use QSELECT to quickly fix this bug after the fact)

[kathleen.132782]

Still the same behavior in LT 2007. Annoying beyond belief.

[Wanderer]

anyone know if this has been addressed in ACAD2007? it's still a pain in 2006.... (thankfully i've figured out how to use QSELECT to quickly fix this bug after the fact)

just confirmed this still happens in AutoCAD 2008.