Skip to main content
Released

Perserve status of Options menu commands of Editor

Related products:FME Form
  • November 18, 2015
  • 3 replies
  • 28 views
takashi
Celebrity
Regarding these commands in the Options menu of the Text / Arithmetic Editor.
  1. Show Line Numbers
  2. Show Spaces/Tabs
  3. Word Wrap
Currently the initial status of those commands (checked or unchecked) is always the same.
I think the most suitable status is different depending on user's preference and the current context that the user is working with, so it would be better if the status that the user has set could be preserved as the next initial status.
Why not inspect features with Visual/Data Preview and Feature/Record Information before writing them into a destination dataset?
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.

3 replies

fmelizard
Safer
Forum|alt.badge.img+22
  • fmelizardSafer
  • Safer
  • November 19, 2015
Hi Takashi,

 

 

We checked and this is already implemented in FME 2016. However, it is implemented per-syntax-type. That is, if you set line numbers on for python, they will be on any time you bring up the editor for python. But if you bring up the editor for XML, then they won't be on. So the options are saved, across Workbench sessions, but by the type of thing you're editing.

 

 

Can you try this in FME 2016 and see if it works for you? Definitely did for me just now, but I was testing on Mac. The team reported it was working for them on Windows earlier today too.
takashi
Celebrity
  • takashiCelebrity
  • Author
  • November 19, 2015
I have tried this with build 16132 64-bit for Windows just now. It worked in most editors as you described, but didn't work in the StringConcatenator and ExpressionEditor. They may need to test more ;)

 

Thanks for the enhancement anyway.
Why not inspect features with Visual/Data Preview and Feature/Record Information before writing them into a destination dataset?
F
Forum|alt.badge.img+1

This has been released as part of FME 2016.1 . Visit http://www.safe.com/downloads to download and try it.

Community Stats

32,750
Posts
124,195
Replies
41,251
Members
Terms & ConditionsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.