Cannot convert source arrow xref to multi-line

Cannot convert source arrow xref to multi-line

Anonymous
Not applicable
1,775 Views
7 Replies
Message 1 of 8

Cannot convert source arrow xref to multi-line

Anonymous
Not applicable

I have just updated from 2013 to 2017 and am not able to change a long string of cross reference line numbers to multi-line.  I am working with a project that was created using 2013, and the text was multi-line then.  Do I need to do some kind of project update?

0 Likes
1,776 Views
7 Replies
Replies (7)
Message 2 of 8

TRLitsey
Advisor
Advisor

Hi there,

 

Is this what you are looking for?

 

Good luck

 

Screenshot - 1_20_2017 , 8_49_29 AM.png

Please mark as a solution if this works for you, kudos are always welcome
0 Likes
Message 3 of 8

TRLitsey
Advisor
Advisor

Or to say it another way ...

 

 

Screenshot - 1_20_2017 , 8_54_03 AM.png

Please mark as a solution if this works for you, kudos are always welcome
Message 4 of 8

Anonymous
Not applicable
I was getting an error in the command line notification error that the text was "not an ATTRIBUTE (you selected MTEXT)". It was already an MTEXT type but the box had been re-dimensioned. I was able to manually put carriage returns into the text area with the enter key but it still wouldn't resize when I dragged the box arrows around.

Brett Ellis
Weigh Price Labeling

Ossid LLC.
www.ossid.com
4000 College Rd
Battleboro, NC 27809
Toll Free: (800) 334-8369 x164
Direct: (252) 446-6177 x164
Cell: (252) 399-9207
Fax: (252) 442-7694
0 Likes
Message 5 of 8

TRLitsey
Advisor
Advisor

I am not clear on this.  Are you just trying to resize area or edit the text?  Is your full tool bar for mtext edit open?  To turn the tool bar on right click in the text box to open the dialog.  And if it is just the box, to you make the size change and then click outside the box?  If you do not exit the editor correctly it will not save the edit, just go back to what it was when you started.

 

Good luck

 

Screenshot - 1_20_2017 , 9_12_29 AM.pngScreenshot - 1_20_2017 , 9_13_17 AM.png

Please mark as a solution if this works for you, kudos are always welcome
0 Likes
Message 6 of 8

jseefdrumr
Mentor
Mentor
I think I understand what is going on here.

When you first change xref text to mtext, ACADE does so without any adjustments to the size of the text area. It will remain the same visually until you do the following:

1. Click into the text as if to edit it. You will see a box around it that represents the text's 'area'.
2. One corner of that area will have little arrows for resizing. At first, they are right on top of one another. Grab one and drag it over.
3. You should now be able to see the hash marks on the ruler, if it's enabled. If not, you should at least see some distance between the arrows. You should also see the text respond accordingly as you drag back and forth.
4. Set it up the way you need it and exit out of the command. Now click on it again. As if by magic, the normal mtext grips are now the way you are used to seeing them. They weren't there before because they were geometrically coincident with each other (meaning they shared the exact same coordinates in space). Their coincidence also prevented you from resizing with the grips.

Hope that helps,
Jim


Jim Seefeldt
Electrical Engineering Technician


0 Likes
Message 7 of 8

Anonymous
Not applicable

That is the correct method, and works fine on an unmodified signal reference until an "Update Signal Reference" is done. At that point, the text will not only loose all previous adjustments made, but also loose the original default width factor - sometimes causing the insertion point to shift. The command no longer works, as described by the OP, because it is already MTEXT. The only solution I can think of would be upon an "Update Signal Reference" command to have any MTEXT revert to single line text, perform the update, and go back to saved adjustments; or enable ACADE to work with multiline text without changing the current settings. 

Message 8 of 8

rhesusminus
Mentor
Mentor

Hi!

 

I believe this behaviour was due to a change in AutoCAD (vanilla) on how automatic line breaks in MTEXT's should occur. Previously, it would break to a new line when it found a comma, but it don't do that any longer.

 

It will however, break on a "space". So, what I've done, is to add an extra space at the end of the cross referencing format, making the multi-line cross references break as expected. Here's my settings.. not the extra space in "/%S.%N ":

2018-02-07_09-44-45.png


Trond Hasse Lie
EPLAN Expert and ex-AutoCAD Electrical user.
Ctrl Alt El
Please select "Accept Solution" if this post answers your question. 'Likes' won't hurt either. 😉