Tuesday, 21 November 2017
  10 Replies
  2.4K Visits
0
Votes
Undo
  Subscribe
How can I get the planting legend to have multi-line text so I can have the width of the legend smaller and for example, my non-landfx legend I have a specification column that I call out the plant HxW and below that the Caliper?
Kyle,

Probably a better solution would be to use the name option "Botanical over Common" to make the schedule less wide.

--J
References
  1. https://jer
6 years ago
·
#1582
0
Votes
Undo
Jeremiah,

I not sure if I understand your response or I didn't explain my question very well. I have a full plant legend with Botanical and Common names (using Botanical over Common), container size, Qty, WOCALs, remarks, etc. and I would like to shorten the legend by having a column called specification that lists the plant HxW and below that the Caliper, instead of having to have two columns one Caliper and one specification

I would also like the Remarks column to have the ability to have multi-line as well.

Thanks for your help.
Kyle,

Remarks already wraps to multiple lines, staying no wider than the Name column.

There are far too many challenges with having two fields appear in one column. The interface design in the Schedule dialog box is the first that comes to mind. Going in the route of having a column able to accept multiple lines brings its own series of challenges -- the interface for viewing, selecting, and editing values, as well as the column title, would all need to support it. As would the ability to choose values -- currently the system pulls all existing field values as a simple choice in a dropdown box for you. If Caliper is embedded within the HxW field, it is just one more complicated solution to pull this off.

Typically your most efficient schedule in terms of size is going to be "Botanical / Common", with "Remarks Below Name".

But you are welcome to send over a schedule example so that we can get a better of what you dealing with, to see if we can come up with anything more specific.

--J
6 years ago
·
#1587
0
Votes
Undo
Jeremiah,

Here is an example of my none landFx planting legend and what I'm looking to have.

Thanks,
Kyle,

Your Remarks column is effectively unusable for anything other than one or two words.
I would have to reiterate what I stated, that a layout of "Botanical / Common", with "Remarks Below Name" is going to leave you with a schedule of the same size, but gain the ability for long remarks if necessary, and not having to stack your Specifications column. That would free you to title the columns as "Ht. x Width" and "Caliper", being a more readable schedule.
I obviously see the benefit to being able to stack certain values, but it is going to be an engineering nightmare, when there is a perfectly sensible solution already available.

--J
6 years ago
·
#1589
0
Votes
Undo
Jeremiah,

Being a new users I'm not sure what you are talking about when you state "Remarks Below Name". I do understand the "Botanical over Common" setting.

Can you show me an example of how close you can get my style of legend to one that LandFX can do?

Thanks,
Kyle,

Please see the attached.
In the schedule dialog box, I chose the option of "Botanical / Common" for the name, and the option "Below Name" for Remarks. Also "Quantity Before Name".
I generated both style options of "Drawing" and "Table", as your example was a little between both.
You can see that by putting the Remarks under the name, it gives more room for comments there, and will automatically wrap as necessary.
Also by having Caliper and Ht x W in separate columns, I would argue it makes a more readable schedule. Also by having Size relocated next to them, it puts all specification information next to each other.

--J
References
  1. https://jer
6 years ago
·
#1592
0
Votes
Undo
Jeremiah,

Thank you for the example. Can I please ask for a screenshot of how you having the settings on the menu?

Kyle
Attached.
References
  1. https://jer
6 years ago
·
#1595
0
Votes
Undo
Jeremiah,

Thank you.

Kyle
  • Page :
  • 1
There are no replies made for this post yet.