Of course, that all works nicely. So I didn’t need to modify the get.field function either?
Thank you.
Of course, that all works nicely. So I didn’t need to modify the get.field function either?
Thank you.
Ah, right. I thought you were on board with having field-names themselves not be capitalized — just all lower-case with underscores rather than spaces. That was the model on which my solution was built.
Unless all your own field-names are capitalized (which might be one way of marking your “proprietary” fields, since TiddlyWiki itself never capitalizes field names, nor do most plugins I’m aware of), it’s confusing to have some be lower-case and some be upper-case. Technically, they’re distinct, but having to remember capitalization differences strikes me as a risky road.
If you’d like a solution that allows for some pattern of capitalized fields, I’m happy to modify my solution. Still, reflecting on when and why you’d want capitalized field names would be a good step here, I think.