QUICK SURVEY.... Text vs. Rich Text use.

[buzzsaw204]

hi,

 

just a quick survey/question...

 

 

what do you use in your practice, of Text vs. Rich Text for??

 

thanks,

[Joe_Carrick]

RT for almost everything

[DRAWZILLA]

me too, rt for everything but some things must use text

[ShaneK]

Text but I'm migrating to rich text and joining Joe Carrick macro club SOON.

[Joe_Carrick]

Labels by default are simply Text.  OTOH, any RTB can have macros and text formatted, colored, filled, etc.

[Alaskan_Son]

Both...but mostly RT.

[johnny]

I use primarly standard text.

[Kiwideziner]

90% RT

[chief58]

RT

[johnny]

I'm surprised so many use RT more often. For me I found tables very difficult to control...and I use a lot of footnotes on my plans. With standard text I simply "tab" to create new column and it stays put even if I need to resize text etc.

RT in CA has been much more challenging IMO.

[Joe_Carrick]

Johnny,

 

The key to using tables in RT is to use a fixed font (Courier New).  Within Macros, I use the .ljust(nplaces) and .rjust(nplaces) methods for each column.

[Northriver]

Rich Text. I am hoping for superscript in the next update.

[Joe_Carrick]

Jeff,  Some superscript (special) characters can be used by pressing the Alt Key and then entering the ASCII code.  Chief also provides some built-in macros for that purpose.

[johnny]

Joe, are you saying that those macros fix the following problem with RT?

 

 

[Northriver]

Joe, can we now properly label our door and window sizes using superscript numerical characters? Is this something new in version X8?

[Joe_Carrick]

Yes,

 

"Test".ljust(20) + "This is a Test to show ........"

"Test doesn't work".ljust(20) + "This will be aligned with the above"

 

because the first part of both lines are padded to 20 characters.

[Joe_Carrick]

Joe, can we now properly label our door and window sizes using superscript numerical characters? Is this something new in version X8?

No, the only superscript characters we can use at present are 1,2, & 3.  All of the other superscript characters require Ruby support for characters above ASCII-255.  CA would need to add UNICODE support to Ruby or provide a custom font with the superscript characters 4,5,6,7,8,9 & 0 in a non-standard location.  This is something I requested but I have no way of knowing if they will do either.

[Richard_Morrison]

I think standard text has a HUGE (to quote Trump) advantage in that the size can be controlled on a dynamic basis by layer. (And therefore, anno set.) Rich text, once placed, is fixed in size.

[Joe_Carrick]

I think standard text has a HUGE (to quote Trump) advantage in that the size can be controlled on a dynamic basis by layer. (And therefore, anno set.) Rich text, once placed, is fixed in size.

Good point - which works perfectly for most Labels.  But for custom data tables it prevents hiliting headings, paragraph titles, etc.  That's where RT shines.

[Kelly_K]

A problem I have with rich text is you have to dig thru the dbx to turn on an arrow, and when you do it comes in unattached.  Unless this was fixed with X8  ( I will say once the arrow is attached it behaves better than the one accompanying regular text).

 

Most of my template text dates to 9.5 which frankly I think performs better with arrows connected than the X series of text.

[HumbleChief]

Text 99% of the time

[javatom]

Almost all text.

[Chopsaw]

Rich Text 95% of the time and Regular text for charts and Hyperlinks.

[MoeGia]

Text almost exclusively.

[dshall]

I think standard text has a HUGE (to quote Trump) advantage in that the size can be controlled on a dynamic basis by layer. (And therefore, anno set.) Rich text, once placed, is fixed in size.

 

Yes,  this has been my thinking.  However I am starting to using RT for boiler plate note blocks.