# Leader text position

**URL:** <https://discourse.mcneel.com/t/leader-text-position/99659>\
**Category:** Rhino for Windows\
**Created:** [April 7, 2020, 1:43pm UTC](https://discourse.mcneel.com/t/leader-text-position/99659 "2020-04-07T13:43:32Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![ivelin.peychev](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/ivelin.peychev/32/676038_2.png) [@ivelin.peychev](https://discourse.mcneel.com/u/ivelin.peychev)\
**Post date:** [April 7, 2020, 1:43pm UTC](https://discourse.mcneel.com/t/leader-text-position/99659/1 "2020-04-07T13:43:32Z")

</div>

Currently leader text is located next to the leader line end.

 ![image](https://global.discourse-cdn.com/mcneel/uploads/default/original/3X/7/6/766428fb0fd1bc8456da987e964a4ff1546fc0c3.png)

This is bad orientation and not according to the standards and best practices. Can it be placed above the line somehow? Can I change the default behavior?

---

<div class="post-metadata">

**Author:** ![wim](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/wim/32/747482_2.png) [@wim](https://discourse.mcneel.com/u/wim)\
**Post date:** [April 7, 2020, 1:47pm UTC](https://discourse.mcneel.com/t/leader-text-position/99659/2 "2020-04-07T13:47:25Z")

</div>

> [@ivelin.peychev](#):
>
> Can it be placed above the line somehow?

Use the `Underlined` option?

 ![image](https://global.discourse-cdn.com/mcneel/uploads/default/original/3X/6/c/6c725fb23a912b155fc0a43a15ef2a1f1720cf9e.png)  
-wim

---

<div class="post-metadata">

**Author:** ![ivelin.peychev](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/ivelin.peychev/32/676038_2.png) [@ivelin.peychev](https://discourse.mcneel.com/u/ivelin.peychev)\
**Post date:** [April 7, 2020, 5:18pm UTC](https://discourse.mcneel.com/t/leader-text-position/99659/3 "2020-04-07T17:18:46Z")

</div>

🤦‍♂️, now I understand why @Dani_Abalde uses a term “McNeel Language”

`Underlined` is a text feature, not annotation feature, for crying out loud!

Also, when you set the position of the text as `Bottom`  
 ![image](https://global.discourse-cdn.com/mcneel/uploads/default/original/3X/9/d/9d184ec67bf90e529d201846e4c484a7c2c61fc6.png)

It should mean the text is below the line.  
Respectively: Top Means above the line and not below it!

Your logic is terrible!

This is the same as Text Justification vs Text Alignment absurd.

---

<div class="post-metadata">

**Author:** ![encephalon](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/encephalon/32/611970_2.png) [@encephalon](https://discourse.mcneel.com/u/encephalon)\
**Post date:** [April 7, 2020, 6:46pm UTC](https://discourse.mcneel.com/t/leader-text-position/99659/4 "2020-04-07T18:46:09Z")

</div>

@ivelin.peychev wim helped you and you thanked it with more complaints. today is fullmoon i guess many are getting kind of crazy.

also i assume that the positioning is meant for the leader instead of the text.

---

<div class="post-metadata">

**Author:** ![Helvetosaur](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/helvetosaur/32/635974_2.png) [@Helvetosaur](https://discourse.mcneel.com/u/Helvetosaur)\
**Post date:** [April 7, 2020, 7:01pm UTC](https://discourse.mcneel.com/t/leader-text-position/99659/5 "2020-04-07T19:01:10Z")

</div>

> [@encephalon](#):
>
> i assume that the positioning is meant for the leader instead of the text.

No, it’s the position of the text relative to its _insertion point_.

---

<div class="post-metadata">

**Author:** ![encephalon](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/encephalon/32/611970_2.png) [@encephalon](https://discourse.mcneel.com/u/encephalon)\
**Post date:** [April 7, 2020, 7:09pm UTC](https://discourse.mcneel.com/t/leader-text-position/99659/6 "2020-04-07T19:09:29Z")

</div>

ok, that is confusing…

---

<div class="post-metadata">

**Author:** ![ivelin.peychev](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/ivelin.peychev/32/676038_2.png) [@ivelin.peychev](https://discourse.mcneel.com/u/ivelin.peychev)\
**Post date:** [April 7, 2020, 7:43pm UTC](https://discourse.mcneel.com/t/leader-text-position/99659/7 "2020-04-07T19:43:24Z")

</div>

😃 see!

also,

> [@encephalon](#):
>
> wim helped you and you thanked it with more complaints.

Wim is McNeel now, he’ll have to (learn to) take the bitter spoon for the confusion in the software.

---

<div class="post-metadata">

**Author:** ![Helvetosaur](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/helvetosaur/32/635974_2.png) [@Helvetosaur](https://discourse.mcneel.com/u/Helvetosaur)\
**Post date:** [April 7, 2020, 8:36pm UTC](https://discourse.mcneel.com/t/leader-text-position/99659/8 "2020-04-07T20:36:04Z")

</div>

> [@encephalon](#):
>
> ok, that is confusing…

Why? The text position has to be relative to _something_. This is CAD, not an illustration or page layout program, and everything in Rhino has control points which tell the program where objects are and allows one to keep track of and manipulate them.

---

<div class="post-metadata">

**Author:** ![jespizua](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/jespizua/32/136739_2.png) [@jespizua](https://discourse.mcneel.com/u/jespizua)\
**Post date:** [April 7, 2020, 8:55pm UTC](https://discourse.mcneel.com/t/leader-text-position/99659/9 "2020-04-07T20:55:08Z")

</div>

> [@Helvetosaur](#):
>
> Why

Because is not the standard behavior. We are talking about annotation, and we are used to think that documentation belong to layout and paper orientation. At least this is how I see it.

---

<div class="post-metadata">

**Author:** ![Helvetosaur](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/helvetosaur/32/635974_2.png) [@Helvetosaur](https://discourse.mcneel.com/u/Helvetosaur)\
**Post date:** [April 7, 2020, 9:30pm UTC](https://discourse.mcneel.com/t/leader-text-position/99659/10 "2020-04-07T21:30:04Z")

</div>

Even in layout space, Rhino objects have control points…

---

<div class="post-metadata">

**Author:** ![jespizua](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/jespizua/32/136739_2.png) [@jespizua](https://discourse.mcneel.com/u/jespizua)\
**Post date:** [April 7, 2020, 9:33pm UTC](https://discourse.mcneel.com/t/leader-text-position/99659/11 "2020-04-07T21:33:15Z")

</div>

Yes, I know… I still find it confusing, but let’s leave it like this 😉

---

<div class="post-metadata">

**Author:** ![encephalon](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/encephalon/32/611970_2.png) [@encephalon](https://discourse.mcneel.com/u/encephalon)\
**Post date:** [April 8, 2020, 7:31am UTC](https://discourse.mcneel.com/t/leader-text-position/99659/12 "2020-04-08T07:31:05Z")

</div>

> [@Helvetosaur](#):
>
> This is CAD, not an illustration or page layout program,

many might not even do any constructional drawings. while the number of these might be sparse, we are still talking about text. when something is called “Leader Text Position” there is no indication of it to be aimed at the insertion control point. not even after using it for years would that have ever crossed my mind. so yes it is unconventional and confusing.

> [@ivelin.peychev](#):
>
> Wim is McNeel now, he’ll have to (learn to) take the bitter spoon

communication does not have to transmit personal frustration. if you try to frustrate others all you get is more frustration. wim did not earn that extra salt, a bit pepper maybe but thats it 😉

---

<div class="post-metadata">

**Author:** ![Dani\_Abalde](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/dani_abalde/32/759411_2.png) [@Dani\_Abalde](https://discourse.mcneel.com/u/Dani_Abalde)\
**Post date:** [April 8, 2020, 7:53am UTC](https://discourse.mcneel.com/t/leader-text-position/99659/13 "2020-04-08T07:53:32Z")

</div>

> [@ivelin.peychev](#):
>
> now I understand why @Dani_Abalde uses a term “McNeel Language”

I say this because every complex system has its vocabulary, not for any other reason. Different people can call the same thing differently, and for efficiency it is convenient to use the same words. And the same word can mean different things to different people. It’s a relative thing that depends on the context, as everyone knows.

It seems simpler than it really is to maintain a consistent vocabulary over the years and with intertwined use cases and several people developing, because the complexity of the reality that one is trying to describe is many orders of magnitude greater than the complexity of the capacity to describe in human language, and if one does not standardize a nomenclature or a taxonomy, these unimportant problems are sure to come up.

---

<div class="post-metadata">

**Author:** ![Helvetosaur](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/helvetosaur/32/635974_2.png) [@Helvetosaur](https://discourse.mcneel.com/u/Helvetosaur)\
**Post date:** [April 8, 2020, 7:56am UTC](https://discourse.mcneel.com/t/leader-text-position/99659/14 "2020-04-08T07:56:58Z")

</div>

> [@encephalon](#):
>
> when something is called “Leader Text Position”

I was talking about text (block) positioning in general, not just leaders. They both use the same naming convention - it would be really confusing if leader text position naming was different from regular text. The leader text insertion point is just the end of the leader.

In the end this is all word play. It doesn’t really matter what you call it, as long as you know what term corresponds with what action. Although there might be some general conventions, there is by no means accordance between _all_ the different software packages as to which term corresponds with which action. (we had this discussion previously over the term “justified”).

---

<div class="post-metadata">

**Author:** ![encephalon](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/encephalon/32/611970_2.png) [@encephalon](https://discourse.mcneel.com/u/encephalon)\
**Post date:** [April 8, 2020, 8:00am UTC](https://discourse.mcneel.com/t/leader-text-position/99659/15 "2020-04-08T08:00:55Z")

</div>

> [@Helvetosaur](#):
>
> It doesn’t really matter what you call it, as long as you know what term corresponds with what action.

i would say it is important that it is intuitively understandable. if there is a broader justification which one might not perceive as such then it is probably not a good method.

---

<div class="post-metadata">

**Author:** ![Helvetosaur](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/helvetosaur/32/635974_2.png) [@Helvetosaur](https://discourse.mcneel.com/u/Helvetosaur)\
**Post date:** [April 8, 2020, 8:06am UTC](https://discourse.mcneel.com/t/leader-text-position/99659/16 "2020-04-08T08:06:07Z")

</div>

> [@encephalon](#):
>
> intuitively

Yeah, but what does _intuitively_ mean? It depends on your frame of reference.

[![](https://global.discourse-cdn.com/mcneel/uploads/default/original/4X/a/6/0/a6034e29f4257e40fde0d94c6317543d87c5981a.jpeg "Frames of Reference (1960)") ](https://www.youtube.com/watch?v=bJMYoj4hHqU)

Is your frame of reference the text block itself, or the insertion point?

---

<div class="post-metadata">

**Author:** ![encephalon](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/encephalon/32/611970_2.png) [@encephalon](https://discourse.mcneel.com/u/encephalon)\
**Post date:** [April 8, 2020, 8:26am UTC](https://discourse.mcneel.com/t/leader-text-position/99659/17 "2020-04-08T08:26:11Z")

</div>

i have to check that video later looks interesting, but i assume its not crucial for the discussion now.

> [@Helvetosaur](#):
>
> Yeah, but what does _intuitively_ mean?

when a stone falls to the ground which probably is true in switzerland nearly the same way as it is true in austria or urugway, then this experience may result in intuitively understanding where the next stone may fall to.

and besides all that groundbreaking wisdom, i see absolutely no reference (on mac V6) other than towards the text itself which is hell of a confusing.

 ![Bildschirmfoto 2020-04-08 um 10.25.13](https://global.discourse-cdn.com/mcneel/uploads/default/original/3X/c/1/c1ddeace1d8b0ce8e8e933f21685ed1bcd27b62a.png)

and having to choose underlined for the text to be above the line is also very weird.

---

<div class="post-metadata">

**Author:** ![Helvetosaur](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/helvetosaur/32/635974_2.png) [@Helvetosaur](https://discourse.mcneel.com/u/Helvetosaur)\
**Post date:** [April 8, 2020, 8:47am UTC](https://discourse.mcneel.com/t/leader-text-position/99659/18 "2020-04-08T08:47:01Z")

</div>

> [@encephalon](#):
>
> and having to choose underlined for the text to be above the line is also very weird

Bottom puts the text ON the 'baseline" (i.e. the bottom of the text is aligned on the baseline) but does not extend the leader under the text.

Underlined moves the text slightly above the baseline and simply extends the leader to go under the text. The text is moved upward to keep it from touching the leader line.

---

<div class="post-metadata">

**Author:** ![ivelin.peychev](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/ivelin.peychev/32/676038_2.png) [@ivelin.peychev](https://discourse.mcneel.com/u/ivelin.peychev)\
**Post date:** [April 8, 2020, 8:49am UTC](https://discourse.mcneel.com/t/leader-text-position/99659/19 "2020-04-08T08:49:38Z")

</div>

> [@Helvetosaur](#):
>
> Is your frame of reference the text block itself, or the insertion point?

I’m sorry I have to give examples from another software but when you’re using non-standardise naming conventions at least the UI should be unambiguous:

 ![image](https://global.discourse-cdn.com/mcneel/uploads/default/original/3X/b/8/b8e12af9a89af5586ae788d77c29b77a6878df1f.png)

Rhino needs to keep up.

---

<div class="post-metadata">

**Author:** ![ivelin.peychev](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/ivelin.peychev/32/676038_2.png) [@ivelin.peychev](https://discourse.mcneel.com/u/ivelin.peychev)\
**Post date:** [April 8, 2020, 8:55am UTC](https://discourse.mcneel.com/t/leader-text-position/99659/20 "2020-04-08T08:55:35Z")

</div>

> [@Dani\_Abalde](#):
>
> It seems simpler than it really is to maintain a consistent vocabulary over the years and with intertwined use cases and several people developing

That’s why there is probably a lead in the dev company that makes the decision to keep or change a certain word/term/numenclature and not leave all these decisions to the programmers.  
The problem with Rhino is not that they are not consistent with these names regarding being the same in all releases, the problem is that they are not consistent with the accepted numenclature and naming conventions in the industries. All engineering disciplines try to be consistent in this and Civil Engineers could understand drawings of Naval Architects or Mechanical Engineers, even Architects because of this consistency. Same have to happen with software these engineers use, and Rhino kinda doesn’t follow this.

> [@Dani\_Abalde](#):
>
> these unimportant problems are sure to come up.

This is as “unimportant” as the `UI Overhaul` discussion! In fact it is part of it.

[Next page](https://discourse.mcneel.com/t/leader-text-position/99659.md?page=2)
