Skip to main content
Solved

TextStroker ignores fme_rotation

  • December 16, 2019
  • 2 replies
  • 46 views

Hey FME'ers,

 

We have a problem with the TextStroker. It seems like it ignores the rotation of our text features.

In attachment an example of our problem.

 

Note that the textstroker doesn't change the fme_rotation but still the text is shifted 180° around a point different than that of the insertion point.

It seems like the problem started since the update to Version_5. With version_4 there is only a slight shift in position (see attachment). I guess we could set back our textstrokers to version 4 to avoid this problem.

Our FME version: 2019.1.3.0 (20191007 - Build 19642 - WIN64)

we use python 3.6+

 

 

Thanks in advance!

Kind Regards,

Louis

 

 

 

Best answer by siennaatsafe

Hello @louisput,

 

Thank you for reporting this issue to us. I've filed an issue entirely under FMEENGINE-62552 for our developers to take a look. I'll follow up once I've heard back from our developers about this. I do think it's best to keep using version 4 until this is resolved or apply a rotator.

 

UPDATE Jan 6, 2020: The issue has been fixed as of 2020.0 build 20098

 

Kind regards,

Sienna

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

2 replies

deanhowell
Influencer
Forum|alt.badge.img+24
  • Influencer
  • December 19, 2019

I am finding the same thing, so just monitoring for an answer. We are using FME(R) 2019.1.2.0 (20190829 - Build 19630 - WIN64)


siennaatsafe
Safer
Forum|alt.badge.img+12
  • Safer
  • Best Answer
  • December 20, 2019

Hello @louisput,

 

Thank you for reporting this issue to us. I've filed an issue entirely under FMEENGINE-62552 for our developers to take a look. I'll follow up once I've heard back from our developers about this. I do think it's best to keep using version 4 until this is resolved or apply a rotator.

 

UPDATE Jan 6, 2020: The issue has been fixed as of 2020.0 build 20098

 

Kind regards,

Sienna