While teaching a FrameMaker class last week, I noted things about the Fm interface that have always sort of annoyed me. (I seem to do this about every year and a half...)
I turned them into a post, complete with images and links to the corresponding Adobe Tracker posts I made. Check out the items I noted in both standard and structured Fm. If you agree with me please take the time to click on the link(s) and vote for the issues.
It's always important to "vote up" things that can make a difference, and it feels like the engineering team is open to some quick fixes right now.
SPOILER ALERT: I’m planning on an update to myWorking with ContentFm reference book soon, and would love to get these UI elements tightened up in time for that next version.
The more recent option toInsert > Imagehas removed the option to copy into document, but the olderFile > Import > Filemethod still exists. Since it’s still there, as with previous versions, the option toImport By ReferenceorCopy Into Documentis placed (illogically) at the bottom of the dialog. Please move to the top of the dialog to promote a user choice that facilitates proper functionality.
In theSpelling Checker(ugh, see next entry…) there is an option labeledExtra Spaces. However, this feature only flags exactly two spaces as a spelling mistake. Either relabel the feature toExactly 2 spaces(easy) or configure it to actually flag two or more consecutive spaces as a spelling mistake.
Well done, Matt! thanks for taking the time to round up these inconsistencies. (one notices, btw, that the Tracker uses fonts I've not seen in any other Adobe interface on my PC …)
I had a thought about the last but one, and don't know whether I managed to add it to my vote: reading the suggestion without knowing the functionality, the two labels are saying different thing. "As is" describes an option to allow adding one of more child elements, the suggestion refers to a single 'insert element' action.