Ciao Mat
I fully agree with you. What you propose would simplify the current
situation to good benefit for many use cases.
Here is a USE CASE: I create a series of several hundred Tiddlers of Film
Title data. Once created a film student will often want to revise the
content of various fields
Mat,
No offence taken, and of course you have the skills to create what you want.
And yes a primitive would be helpful, but one can be built without a submit
button could be created.
The edit fields solution I am working on allows you to simply add "text" to
the list of fields in a field on
@Tony. Sounds interesting. Note that any user *can* of course manually
create a "field with a submit button" but my point is that it should be
built into core as a primitive. So I'm not really interested in seeing some
neat macros that I probably could have created myself. I, of course, have