Tuesday, 25 July 2017
  7 Replies
  2.4K Visits
0
Votes
Undo
  Subscribe
When we have more than one line per plant on our plant schedules, the symbols end up out of alignment with the text (as shown in attached jpg). Are we doing it wrong?
Katherine,

Yes, it looks like the trunks on the symbols should be landing in the middle of the top row (botanical), not 1/4 down the bottom row (common).

I've passed this along to our development team to look into and update.

Thanks for pointing it out!
-Amanda
6 years ago
·
#1327
0
Votes
Undo
Thanks, Amanda!
This has been fixed, and will be part of the next update, no later than Friday.

--J
6 years ago
·
#1365
0
Votes
Undo
Still getting funky schedules (see attached). This was a concept schedule, haven't checked to see if i'm getting similar results with the regular planting schedule.
Katherine,

It's hard to tell what is amiss, if anything from just a screenshot.
If you are using an SHX font for the Concept Schedule Text font, you can try using a TrueType font instead.
Other than that, can you be more specific with what aspect of the symbol spacing is off for you?

--J
6 years ago
·
#1367
0
Votes
Undo
Yes, our office uses a SHX font as our standard font on all of our construction documents.

It appears to be the same issue from earlier in this thread- the symbols are not aligning properly with the text. Look at where the hatched rectangles are in relation to the text that describes them-- they're not centered on the text, nor are the tops of the rectangles aligned with the top of the text.
The issue from the original post, is that with Common Name below Botanical Name, the system was lining up the image with the second line instead of the first.
This issue looks more like the "symbol drift" that occurs with SHX fonts.
As I said, you can try using a TrueType font, to confirm whether or not that is the issue.
Further, if you use the Tech Support feature in the software, you can send the file in to us, so that we can best replicate the issue.

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