There are hundreds (thousands?) of parameters.Maybe thinking too naively about this…I actually don’t understand why this is challenging. As far as I know all of these features are already documented. It should be straightforward to e-link the relevant sentences/paragraphs in the doc to tool tips.
Perfect job for an intern.There are hundreds (thousands?) of parameters.
It's not a trivial task...
No I get that, but it’s a one-time investment. Whenever documentation changes tool tip gets modified automatically. New features will be incremental to the baselineThere are hundreds (thousands?) of parameters.
It's not a trivial task...
If tool-tips were a line or two, probably not "hard" and interns could do it.Perfect job for an intern.![]()
Yeah, a hyperlink to the appropriate manual section could work, but maybe only if the PDF manuals were packaged with AE so they would be more tightly integrated. I don't know if that would appeal to FAS or not.Even a hyperlink to that specific section in the owners manual would be a welcome addition.
I'm all for the basic idea, especially if the user would be able to edit them, but you know the next request will be to have 10 languages... On and on...Maybe thinking too naively about this…I actually don’t understand why this is challenging. As far as I know all of these features are already documented. It should be straightforward to e-link the relevant sentences/paragraphs in the doc to tool tips.
The issue with the Wiki might be that it’s not official.Of course there's also a lot of supplemental information in the wiki as well, so that would be left out.
Of course. Hence a community-sourced optional file that could be loaded into AE - with the disclaimer that it is not FAS official (unless & until it was vetted and included as such).Thinking that this wouldn't come with a maintenance burden is naive.
So was building the Great Wall of ChinaNo I get that, but it’s a one-time investment.
How? What mechanism would do that? Also, documentation updates often lag behind firmware updates...Whenever documentation changes tool tip gets modified automatically.
That could possibly work. There would probably need to be limitations on amount of text, formatting, etc since it has to fit within the editor display.Another option is a community/user sourced XML/JSON doc with tool-tip data, after determining a suitable schema and naming convention.
This could be configured in AE (e.g. in Preferences/Workspace) to point to whatever tool-tip file and eventually be included in the release (with option to be overridden by users as desired).