I support you, in all your observations.
except this one
We all have our opinions, and they need to be shared here.
You could have formulated this opinion differently.
We all have our opinions, and they need to be shared here.
I don't believe in running my mouth without being willing to help fix the problems I'm pointing out.
Agreed. Admonition icons shouldn't be more than 2 to 3 ems square (an em, if you are not aware, is the width of "m" in the default running font). They should draw attention, but not shout for it.in general I think it is a good idea to have an ability for a soft "attention" in running text, that is a common used technique in several types of documentation
it really should be a small indication, the ones that are interested in it will quickly learn to spot them even if they are very much deemphasized.
- most icons in fc are made for fc, so why not have an icon made for this?
- is not the "info" icon more widely recognized?
- is there any chance that you can work on the current "banner" templates, like obsolete/warning etc, they are imho too similar as it is today.
I don't disagree with what you just said even a little bit. But there's a general principle about this kind of choice that you should bias your defaults to be friendly to new users - which means simple projects with a low recompute time. The UI design error here is not having an auto-update option, it is defaulting that option to "off" rather than "on".not really, search to forum for requests to completely turn off recompute...
so the behaviour today is the adjustment to what is reasonable for "modern processors", when models/assemblies reach a certain size or complexity one really want to be in control of recomputes at user side.
That is really good, creative thinking!with that said, here is a random thought for a mechanism that would take care of new users...
put a timer on recompute (should not be hard to do coding wise) and make a user preference for max recompute time.
then for all documents in session the setting will be to force recompute always, until that first max time is hit, when it goes to current default behaviour (if one wants to make it easy coding wise I suppose one just lets it there until the document is closed, or make it a bit more intelligent, so that if things are deleted the flag will be retested and setting adjusted).
that would quite likely take care of the majority of the "dangerous curves" for newcomers,
and it would be in line with your (in other post) principle of not doing it in documentation
Agreed!at last, if there is some demarkation in running text, there should also be a category attached to it, so that new users could simply browse that category, i.e. it would be one convenient avenue to gain ability for new users to explore an overview of common pitfalls at their own behest.
Fair enough.
Then the dangerous curves icon is not the right choice. The most familiar warning icon (in relation to computer software) would be a black exclamation mark on a yellow background.