From: Ethan A M. <me...@uw...> - 2020-01-21 04:44:13
|
On Monday, 20 January 2020 18:18:57 PST Dima Kogan wrote: > Thanks for the explanation. That sounds very suprising to the user. Can > we at the least document this behavior in "help border"? Ideally it'd be > controllable in "set border" somewhere too. Is this something that > wasn't done on purpose, or has nobody gotten around to it? These lines are drawn unconditionally in the routine draw_3d_graphbox() graph3d.c:2450ff I have no objection to adding a corresonding flag bit (for all of them) in the "set border" command or even four flag bits (matching the four vertical edges of the full graph box). But the flag bit[s] would have to default to "on" for backwards compatibility. On the other hand, looking up the bits one by one is inconvenient. It might be more user-friendly to add a keyword set border <bitmask> {{no} somethingdescriptive} I can't think what to call these lines, however, so I have no good suggestion for what that "somethingdescriptive" keyword might be. "surface anchors"? "drop lines"? "partial edges"? Ideas? > > dima -- Ethan A Merritt |